Remove wordpress-default from base repository in favor of wp-cli

WP-CLI allows for more flexibility when setting up an initial development environment for WordPress. Removing the wordpress-default directory allows for us to start prepping for this addition
No longer need to ignore the wordpress-default directory
Initial installation and use of wp-cli to setup default WordPress

Download and install WP-CLI, then use it to download and configure a default WordPress environment to start the vagrant with.
Install wp-cli and use it to configure an initial WordPress setup

This replaces our original WordPress setup that had been included with the repository with an installation of wp-cli. Wp-cli allows us to install a custom configuration on the fly and will go a long way toward an environment where WordPress installs can be setup dynamically.

SO SWEET!
Use yes yes instead of printf yes to pass option to pecl
Updated README

* Had missed @tddewey as a contributor, added
* Added contribution instructions for develop branch
* Update Vagrant version to 1.1.2
Go through full installation of WordPress default site

Rather than leave the site hanging for details, configure it and install it. This does require moving this section of code down below the service restart area so that mysql is available for wp-cli to use.

Next, we'll see what we can do about getting this data from a project config file
Install subversion on vagrant up for future use
Bump version of Vagrant to 1.1.3
Bump Vagrant version to 1.1.4 - 1.1.3 had a networking issue
Add Mockery

Add PEAR installer for Mockery (unit test framework).
Merge branch 'develop' into local
Merge branch 'master' of github.com:jeremyfelt/varying-vagrant-vagrants into develop
Change 'guy' to 'user' in sql sample

This is a little bit splitting hairs, but it seems inappropriate to gender a db user.
Stop the apt-get update flag for 0.3

The check to see if apt-get update had run in the past is a good idea, but fails in practice if you destroy the vagrant box and then run vagrant up again from time to time due to the package source files expiring.

We'll solve this in a different way in the future, but for now it's too shaky to include.
Updated README for 0.3
Merge pull request #27 from jeremyfelt/develop

Merging v0.3 from develop branch
Updated README version to 0.4-working
Merge branch 'master' of github.com:jeremyfelt/varying-vagrant-vagrants into develop
Replace PEAR with Ubuntu packages and composer