[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
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.
Merge pull request #13 from action-io/encrypted-data-bag-secret

Add encrypted_data_bag_secret_key_path to the Vagrantfile if present
Shorten long line in VagrantfileCreator.
Use path relative to kitchen_root for encrypted data bag secret file.
Merge branch 'add-vmware-support' of https://github.com/intoximeters/kitchen-vagrant into intoximeters-add-vmware-support

Conflicts:
	lib/kitchen/vagrant/vagrantfile_creator.rb
Fix up README lines.
Recommend the vagrant-wrapper gem in README.

This could help people manage projects with older vagrant gem
dependencies and newer projects that require the package install of
Vagrant.

Closes #19
Added prototype Puppet support