Unit Tests: switch to using `develop.svn.wordpress.org` for the travis-ci test environment instead of `unit-tests.svn.wordpress.org`.

`unit-tests.svn` is a deprecated repo and `develop.svn`'s test suite has diverged from it to the point where there are a couple of important differences in the test environment that affect how BuddyPress unit tests are run on travis-ci; the defaults for `error_reporting` and handling of functions that have been marked as deprecated.

Recent commits such as r8015 have been successful in adjusting the `error_reporting` level but our tests that have been marked as `@expectedDeprecated` are currently not handled correctly on travis-ci and on any local testing environments that use `unit-tests.svn` along with a development `error_reporting` level.

A consequence of switching the travis-ci script to `develop.svn` is that, as the WP core-to-develop SVN restructing happened between WP 3.6 and 3.7, SVN versions of WordPress prior to 3.7 don't have the seperate `src` and `tests` folders which the updated travis-ci script relies on. The tradeoff is that we'll have increased confidence in our travis-ci environment going forwards.

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8017 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Unit Tests: on travis-ci with PHP 5.5.*, don't run the tests with `WP_DEBUG=true`.

PHP 5.5+ uses the `ext/mysqli` library and as versions of WordPress older than the current trunk don't support `mysqli`, PHP throws a bunch of `E_DEPRECATED` warnings about the use of the deprecated `ext/mysql` library. Because we test several versions of WordPress against several versions of PHP, combinations occur with old WordPress and new PHP, which causes these deprecation notices, causing failures.

A better solution would be to somehow suppress `E_DEPRECATED` warnings in the phpUnit configuration or change the error levels that `WP_DEBUG` sets, but so far I've been unable to find a way to do this. For now, travis-ci tests against PHP 5.5 will run with `WP_DEBUG=false`; this is actually the environment we've been testing in on travis-ci until very recently (see r8015).

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8018 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Unit Tests: fix undeclared variable warnings when running multisite tests

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8019 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Blogs: fix undeclared variable in `BP_Blogs_Blog->search_blogs()`.

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8020 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
xProfile: change the field visibility JS to show/hide the controls immediately, rather than with a slide/fade transition.

This helps improve the perceived performance of the visibility
controls. The code quality of these parts of the JS has also been
improved.

Fixes #5439

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8021 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Caching improvements related to bp_core_get_user_displayname()

- The cache check in BP_XProfile_Data::exists() should be aware that cache
  misses are stored as objects and check for misses accordingly
- Ensure that fullname cache is busted when field 1 is updated
- Some unit tests

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8022 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
Improve cache test for BP_XProfile_ProfileData::exists()

git-svn-id: https://buddypress.svn.wordpress.org/trunk@8023 cdf35c40-ae34-48e0-9cc9-0c9da1808c22