[berkshelf] Berkshelf is for Workstations

This makes the Vagrant driver behave more like the LXC driver, relying on the SSH Base semantics set forth in test-kitchen@1.0

I prefer to have berkshelf resolve cookbooks on the workstation -- temporarily install them somewhere, and then have an intermediate system, in this case, TK, ship cookbooks and so-on from a combined, resolved, cookbook directory. Previously Vagrant was trying to interact with Berkshelf on the guest, which would mean that the guest would need to have access to Git, etc
[berkshelf] only configure the home directory etc if not using Vagrant directly for provision
[berkshelf] Hack the synced folders
[berkshelf] use_vagrant_provision toggle for chef  related functionality, enhance synced folders
[synced_folders] Fix quotes in Vagrantfile generation
Add encrypted_data_bag_secret_key_path to the Vagrantfile if present
Support berkshelf-vagrant 1.1.0+ in Vagrantfiles.

With an assist going to @petejkim
Merge pull request #15 from opscode/berkshelf-vagrant-1.1.0-compat

Support berkshelf-vagrant 1.1.0+ in Vagrantfiles.
Add explanation in README.
Release 0.8.0, seattlerb edition.
Up version for development.
Update Berkshelf plugin detection

Berkshelf has recently renamed their Vagrant plugin which is already updated in master, but this detection of the old plugin will prevent a kitchen run.
Merge pull request #16 from martinisoft/fix_berkshelf_detection

Update Berkshelf plugin detection
Release 0.9.0, plugin renaming edition.
Up version for development.
Add multiple provider support to Vagrant driver
Add VMware support to VagrantfileCreator

Add support for VMware in the VagrantfileCreator class by breaking out
the customization logic into separate methods for Virtualbox/VMware.
Update documentation for VMware
Merge pull request #12 from fujin/feature/berkshelf-is-for-workstations

[berkshelf] Berkshelf is for Workstations
Update README with new config options.