Add credentials for various pieces to the README
Add link to MySQL wiki page
Append a custom sources list to the default provided for Apt

Some of the packages included by default with the sources list in Ubuntu 12.04 are way out of date, or boring at the least. This commit allows custom sources to be appended to the list so that we can better control the versions that are installed.

A specific change from this commit is the use of SVN 1.7.9, which should help to resolve file permissions issues on some Windows machines.

Closes #58
Install unzip package during provisioning
Updated CHANGELOG for upcoming 0.6
We no longer use the apt_update_run check
Improved documentation for database import process in bash script
Add group write permissions to wordpress-unit-tests directory

Avoids having to use sudo to do things as the vagrant user with WordPress unit tests.
Add group write permissions to wordpress-trunk and wordpress-default

Allows for easier file manipulation from with the virtual machine without the use of sudo.
Be specific with directory and file permissions when mapping /srv/www

Rather than manually chmod specific directories to have group write access, map the /srv/www directory initially with 775 on directories and 664 on files. This allows for non sudo access to a bunch of stuff.

Reverts previous commits adding chmod statements.
Set a default WP_TESTS_DIR path

PHPUnit relies on a WP_TESTS_DIR path when running outside of the actual tests installation. This provides for that.
Check out wp-cli to /srv/www using composer instead of phar
Composer is already available at this point in provisioning

Now that we're using it for WP-CLI though, we may want to remove the flag that allows the disabling of the composer install.
Up permissions on files in srv/www to 774 so that wp-cli can execute

This is a blanket fix and should probably be thought of more as we go. It doesn't really cause a security issue because this is all happening inside a VM on your local machine, but it's still worth thinking about.

One option is to not explicitly set dmode and fmode when mapping the directories and then handling that part manually through creative uses of chmod.
Use bash_profile for environment vars rather than bash_aliases

Per @danielbachhuber's comment on bbc25f8 - environment variables make more sense in bash_profile.
Move environment variables back to bash_aliases

bashrc is ignored if we use bash_profile. This causes bash_aliases to not be included. We could include bash_aliases in our bash_profile, but we would then miss all of the default stuff provided by the VM in bashrc
Reintroduce bash_profile to handle environment vars...

...but handle it properly this time. If bash_profile is detected, then .profile is not loaded. Normally .profile sources .bashrc, so we should account for that as well.
Use the full path to wp-cli during provisioning

Something in the bash_profile changes caused our alias for wp to not be available during provisioning. We can use the full path during provisioning and still have `wp` aliased properly once things are setup.
Link /srv/www/wp-cli/bin/wp to /usr/local/bin/wp

This allows `wp` to be used freely without worrying about bash_aliases being loaded during provisioning. Worth keeping an eye out for consequences of this change, but it seems ok right now.
Update to CHANGELOG