Bump VirtualBox version to 4.2.10
Merge pull request #18 from ericmann/vvvv-0.2

Install PEAR PHPUnit package during provisioning
Only run apt-get update on first boot

apt-get update is the part of the `vagrant up` process after a `vagrant halt` that takes the longest because it will go out and update all of the source lists. Because we are not installing anything extra, we can skip this if it has run before.

On first boot, we create an empty `apt_update_run` file in our /srv/config directory. Subsequent boots will see this file and then skip the update command
Clean up apt-get installs in provisioning script

The provision script was so cleverly split up into many `apt-get install` statements, which was great but caused a little bit of a delay in processing each time so that it could gather the package data.

This commit combines all of those packages into a bash array that we pass to one `apt-get install` command so that the entire shebang can be completed at once.

In additon, some whitespace stuff has been cleaned up in the output because pretty output is better than ugly output.

Closes #20
Use smarter file exists check instead of cat

Per @thelastcicada, this is a much smarter (and easier) way of checking if the file exists
Support database names with hyphens in import-sql script

The bash script that helps us import backup SQL files into existing databases that have been created with init-custom.sql was choking on databases with hypens in the name. This performs a little magic by assigning the SQL statement to a variable first before going about the commands as normal.

Fixes #19
Updates to remove Vagrant 1.0.x warnings
Merge pull request #21 from carldanley/vvvv-0.2

Use the new v.* config parameters for Virtualbox specific configuration, allowing us to ditch all 1.0.x configs.
General cleanup of provision.sh with comments

A little house cleaning on the provisioning script to better organize and describe where and why things were happening.
Prevent "stop: unknown service:" error during `vagrant up` after `vagrant halt`

mysql gives us an error if we restart a non running service, which happens after a `vagrant halt`. Check to see if it's running before deciding whether to start or restart.
Check for SQL files before for loop parsing those files

Avoids an error when booting with a fresh `vagrant up` when no custom sql files have been added to /database/backups
Check for init-custom.sql before importing

Avoids errors on a fresh `vagrant up` where an init-custom.sql file has not been created yet.
Add ack-grep to provisioning, because ack is better than grep
Stop watching init-custom.sql for changes

It doesn't make sense, especially with our new data structure, to reimport all DBs whenever the init-custom.sql file has been modified. We're planning for a smarter way of importing new projects in the future, but for now we'll have to live with mysql commands to create databases after a vagrant up - or... just halt the box and bring it back up again.
Add documentation to the watchr.script

Explain some of the obvious if somebody comes browsing through.

We might need to do some additional testing on the xdebug process and see what gets restarted automatically when those files are copied back and forth
Update README for v0.2

Clarifies a few things and refactors the README to be less of an expirement and more of a real thing
Merge pull request #23 from jeremyfelt/vvvv-0.2

Merging v0.2
Mark develop branch as v0.3-unstable
Update README with latest intro blog post
Merge remote-tracking branch 'origin/master' into develop