upgrade Vagrant 1.1+; use standalone omnibus cookbook

We now use an `omnibus` cookbook that lives in the opscode-cookbooks
organization (and is released to the community site). Vagrant support
has also been removed from the bundle and upgraded to use Vagrant 1.1+
which is now installed system-wide.
Update example omnibus config files for new config format

The Omnibus config file is now `mixlib-config` based.
Projects are now built using the `omnibus` CLI
`Omnibus.root` is now `Omnibus.project_root`
`omnibus` cookbook is now pulled in using Berkshelf

The `omnibus` cookbook has been refactored and lives as a properly
released cookbook (along with it's dependencies) on the community site.
update dna.json files for new attribute naming

https://github.com/opscode-cookbooks/omnibus/blob/master/attributes/default.rb
gitignore some additional build-time tmp assets
trailing whitespace and typos
use a different dna.json file for solaris2 build slaves

The Solaris build slaves use a jenkins/build user of `jenkins` as
`jenkins-node` is too long of a username for Solaris 9!
capitalize windows build user to `Administrator`

The Chef user resource will attempt to create a new user account if the
lowercase `administrator` is used.
change json attribute naming to dna-PLATFORM.json

Call me a pedant but I like natural sort order.
Ensure the installed cert authority is loaded on windows
temporarily point at WIP versions of some upstream cookbooks