Move msi building logic into omnibus-ruby as a packager.
Clean the build_iteration & handle + in the windows artifact names.
Move the msi version setting into omnibus-ruby.
Pick omnibus-ruby with msi packager support and latest omnibus-software.
Merge pull request #152 from opscode/sersut/msi-packager

Refactor msi building logic into omnibus-ruby as a packager
Update chefdk-win project to match *nix changes
Fix build issues for chefdk on win (WIP)

NB: this is pretty rough and probably breaks existing projects
(chef-client). Needs to have configurable behavior for generating batch
file wrappers for chef executables at minimum.
Pull in latest omnibus-sofware w/ win chefdk fixes
Change ruby-windows back to 1.9.3 w/ override for chefdk
Remove bundler from top-level, this was a bad attempt at a bug workaround
Remove commented bundle install code
Update omnibus-software for bundler dep fix
Move md5 override for ruby-win to software defn.
Workaround issue cause by conflicting PATH environment variables

cmd.exe can have both a PATH and a Path environment variable; setting both
causes unpredictable behavior. We work around this by detecting the
correct path variable to override in shell_out commands.
update omnibus software to pull in cmd.exe related fixes
No need to specify full box URLs with `kitchen-vagrant`
Expand platform matrix in build lab
Ensure local code is synced into build lab

If you would like ongoing changes on the host to be reflected
on the guest VMs you can use `vagrant rsync-auto`:

  $ cd .kitchen/kitchen-vagrant/chef-ubuntu-1204/
  $ vagrant rsync-auto
  ==> default: Doing an initial rsync...
  ==> default: Rsyncing folder: /Users/schisamo/dev/code/opscode/omnibus-chef/ => /home/vagrant/omnibus-chef
  ==> default: Watching: /Users/schisamo/dev/code/opscode/omnibus-chef
Update README with latest details on Kitchen-based build lab
Remove invalid `build_dir` attribute from .kitchen.yml