Add a Vagrant 1.1 build lab to generated projects

This lab consists of a `Berksfile` and `Vagrantifle` dropped into the
root  of every generated project.

The `omnibus` cookbook (and it's dependencies) now live external to this
repository (as they should). The `omnibus` cookbook also depends on
plain, old upstream community cookbooks and will be released to the
community site.
remove legacy Vagrant plugin

The previous vagrant plugin that shipped in `omnibus-ruby` is sorely out
of date now that Vagrant 1.1 has shipped. For ease of maintenance it
makes more sense to just add a shell provisioner to project Vagrantfiles.
Multi-VM workaround for `berkshelf-vagrant` plugin

Currently `berkshelf-vagrant` doesn't work correctly with multi-VM
Vagrantfiles. The current workaround is to add a
`config.berkshelf.berksfile_path` to each vm.define block.

More info here:
https://github.com/RiotGames/berkshelf/issues/436#issuecomment-15394731
https://github.com/RiotGames/berkshelf-vagrant/issues/4#issuecomment-15979246
ensure `Omnibus::VERSION` is loaded when omnibus is required
relax s3 config validation

Software is cached in the S3 bucket with public_read ACLs so it possible
to take advantage of s3 caching without an access key and secret key set
in the Omnibus config.
prefix generated project directory with `omnibus-`

This follows the recommended Opscode convention:

* omnibus-chef
* omnibus-chef-server
ignore the Berksfile.lock by default in generated projects

The `omnibus` cookbook already locks versions down fairly tight.