initctl stop chef-server-runsvdir leaves orphaned processes

The right thing to do would be to have 'kill signal HUP' in
the Upstart config so everything gets taken care of cleanly
when you use upstart to stop the runsvdir process. But that
stanza isn't available in Ubuntu 10.04. Without that stanza
Upstart sends a TERM which kills runsvdir and orphans all the
rest of its process tree.

This fix does the same thing Enterprise Chef server does. It
stops Chef services in a pre-stop script.
Update CHANGELOG with note about fix for PR 73
Merge branch 'mm/fix_chef-server-runsvdir.conf'
Updated Omnibus 2.0 with minimal metadata fixes
Vendor `chef-gem` and `libffi` software definitions

Ohai 7.2.0 was just released and has a dependency on the `ffi` gem which
ships with a native extension which requires `libffi`. The fix is to add
a proper dependency on `libffi` in the `chef-gem` software definition.

We can’t simply update to the latest ominibus-software as this project 
is still on Omnibus 2.0.x. The alternate is to vendor the affected 
software definitions tweaked for the Omnibus 2.0 DSL.
Merge pull request #80 from opscode/schisamo/chef-requires-libffi

Vendor `chef-gem` and `libffi` software definitions
Fix the paths in the wait-for-rabbit script
Update Changelog with note about fix for wait-for-rabbit script
Merge branch 'mm/fix-rabbit-wait'
Postgres must be running before we can add users
Update sqitch verify command used during upgrade

We try to run sqitch verify to determine if sqitch is on a box during
upgrade. With the recent lock down of postgres, this needs to be run as
the db_user or else it will fail with an error, making the upgrade
process think sqitch isn't on the box, when it is.

Added a comment about this issue in the code as well to clarify this
issue.

Also removed 2 from the possible return values, as verify won't return a
2 (that's an issue with the sqitch deploy command in some cases).
If epmd isn't running, continue with upgrade, as that is desired state.

Previously, if epmd wasn't running, the upgrade would fail trying to
stop epmd. Since the desired state is that epmd not be running, we don't
care how it got that way, just move on with life.
Maintain postgres state during a reconfigure
Add comment about attribute being compile time evaluated.
Merge branch 'mm/fix-upgrades'
Update CHANGELOG

Includes info about fix for Chef Issue 1595, chef-server-ctl upgrade
fails with version 11.1.3
The chef-server attributes includes `despsolver_timeout` but that
value wasn't applied anywhere. Changed that value to match the
hard-coded value, 2000, at

    https://github.com/opscode/chef_objects/blob/master/src/chef_depsolver.erl#L46

and updated erchef.config to use that value per

   https://github.com/opscode/chef_objects/blob/master/src/chef_depsolver.erl#L127
The desired default for the depsolver timeout is 5000

This matches what is in enterprise chef and this will keep open source
consistent with enterprise chef in this area
Merge branch 'mm/depsolver_timeout'
Update changelog with note about depsolver_timeout attribute fix