rubygems-customization before ruby-windows-devkit

Fixes chef-dk#100

rubygems-customization drops in a custom operating_system.rb, after the devkit install
has modified the regular version of this file. However, if we install the devkit after
we place this file, the devkit will modify the custom version.
Move chef-vault into omnibus-chef

This software formerly lived in omnibus-software, but was failing tests because
it has dependencies on the softwares in omnibus-chef.
Merge pull request #193 from opscode/btm/devkit-fix

rubygems-customization before ruby-windows-devkit
Output a SemVer compliant build version string

We currently use the `:git_describe` version for all chef-client 
projects. This build version format does not respect 
`Omnibus::Config.append_timestamp` which in turn causes two different 
builds to produce packages named identically. This can wreck havoc on 
when packages are published to backends like Omnitruck and Artifactory.
Merge pull request #192 from opscode/schisamo/use-semver-everywhere

Output a SemVer compliant build version string in all Client projects
bump gem versions
Merge pull request #206 from opscode/sethvargo/chef-vault

Move chef-vault into omnibus-chef
Merge pull request #217 from opscode/lcg/bump-gem-versions

bump gem versions
bump gems

pins omnibus to the 3.0-stable branch, pins omnibus-software
to omnibus/3.2-stable branch
Merge pull request #219 from opscode/lcg/update-gems

bump gems
fork projects for chef-12
Bump knife-spork version to 1.4.1
Merge pull request #222 from jonlives/master

Bump knife-spork version to 1.4.1
fix chef11 project names
nuke Opscode from orbit
2014
Merge pull request #221 from opscode/lcg/chef12-fork

fork projects for chef-12
Pin chef and test-kitchen versions.
Hardcode ruby devkit into Windows customization

Fixes chef-dk#100 by adding hardcoding the necessary bits for the devkit
into the operating_system.rb file that we currently create to ensure gems
are installed into the users directory on Windows. Also reverts 5b99247,
as it proved only half of a solution, the other half being complicated
balancing of build-order to make sure rubygems-customization happened at
exactly the right time (before devkit, but not before bundler, at least).
Make sure the aux gems are installed into the embedded directory.