Add a project to build chef in separate directory

We cannot install vanilla omnibus packages on the machines that build or
test omnibus packages because they conflict over the /opt/chef
directory. We could install w/ rubygems but on some platforms omnibus is
the only viable method we have for building chef and all of it's deps.
Therefore, we need a secondary chef package that we can use to manage
the omnibus build and test machines.
Update angrychef project for more required fields
bump omnibus-ruby and omnibus-software

- omnibus-ruby: solaris builds using pkgmk instead of fpm
- omnibus-ruby: support for tar.xz files (unused in omnibus-chef)
- omnibus-ruby: support for pre-install scripts (unused in omnibus-chef)
- omnibus-ruby: bump default ncpus to 3 and jobs to 2 (build parallelism)
- omnibus-software: chef windows/unix gemspec split
- omnibus-software: /opt/chef/bin/ohai missing fix
- omnibus-software: ENV['OHAI_GIT_REV'] support
- omnibus-software: numerous aix fixes
- omnibus-software: make -j everywhere
only install the windows gem on windows

- we build both now due to the split gemspec, need to only install
  the windows version
numerous fixes for install scripts

- conditionally setup symlinks for chef-10-vs-chef-11
- syntax fixes for solaris
test for symlink presence

nothing else in the infrastructure tests for the symlinks getting
setup correctly, so we do that here.

- we clean up the symlinks from the previous install which may have
  been left behind due to bad/missing/whatever postremove scripts
- we test for the presence of the symlinks after installing the
  package
- for now only test for the ones in common
Merge pull request #92 from opscode/OC-8537

Oc 8537
New opscode logo for windows msi installation.
Merge pull request #94 from opscode/OC-10052

New opscode logo for windows msi installation.
bump omnibus for solaris pkgmk fix
bump omnibus
bump omnibus
Merge pull request #96 from opscode/OC-8537

Oc 8537