Initial add of phpMyAdmin installation to default web

Developers transitioning from tools like MAMP are often using phpMyAdmin as part of their workflow. This commit grabs the 4.0.3 version of phpMyAdmin and extracts it for use in the http://192.168.50.4/database-admin/ tool.
Update README and CHANGELOG to reflect phpMyAdmin addition
Add Bootstrap to boostrap a simple navigational page for tools included with VVV

I know... but it's easy.
Start getting ready for a Boostrappy display
Basic build out to beginnings of dashboard page
Add other tools to new default navigation
Update wp-cli on during provisioning

No sense in letting wp-cli get stale on us. Using rebase here to throw a smarter error when there are unstaged changes in the wp-cli working directory. Not sure if that's best, but it'll do for now.

Closes #82
Set WP_DEBUG with wp-cli extra-php parameter

Now that we're updating wp-cli on provision, we have access to the new extra-php parameter in wp-cli. This allows us to add PHP code to the wp-config.php file as it is created by wp-cli through the use of here-docs.

Here-docs are ugly and screw with the indentation of the provision.sh file, but that's cool. It might be worth piping in PHP from a file if possible and if we ever get to the point where we need something more complicated set.

Closes #81
Refresh inline provisioning docs
Update Composer on every provision instead of tracking on commit hash

Tried to get fancy by tracking the commit hash, but that was pretty dumb. The hash gets older and the installations created via VVV get newer and newer...

Go back to the method where it updates on every `vagrant up` or `vagrant provision`
Enable Xdebug autostart by default

It's usually annoying to remember that a specific GET or POST parameter is required when initiating a remote Xdebug session. Because we have Xdebug turned off by default, it doesn't seem to hurt to have autostart enabled when Xdebug is turned on.
Always enhancing the README...

May need to go back in and add some links to Wiki articles. I'm on a plane.

Still working on the best way to describe how to use VVV, but I think this comes a lot closer.
Bump version number of WordPress in the README

Since `provision.sh` [links to latest.tar.gz](https://github.com/10up/varying-vagrant-vagrants/blob/master/provision/provision.sh#L295), it's now automatically pulling in 3.5.2 -- README is out of date.
fixed some spacing issues that have been bugging me for months
Merge pull request #87 from carldanley/master

Fix some spacing issues
Merge pull request #86 from kadamwhite/upgrade-wp-version-number

Bump version number of WordPress in the README
Capture a ping_result to determine network status

Capture a basic ping result to one of Google's DNS servers to try and determine if outside access is available to us. If it isn't, we'll want to skip a few things in the future rather than creating a bunch of errors.
Wrap major update/installation procedures in network check

If we don't have a network available to us, we should skip some of the updating and installing that happens throughout the provisioning script.

In a future commit, we'll want to provide some additional information about the boot process, including this network status.
Get with the syntax, yo.
2 pings is enough to determine network availability.

I'll trade a bit of accuracy for a bit of speed in this case. If you need 3 pings to establish network connectivity, then your network needs a hug.