add support for disabling the timestamp in build version

If the OMNIBUS_APPEND_TIMESTAMP environment variable is unset or set to 
a truthy value we will append a timestamp to the build version.  This 
behavior can be overridden by setting this value to a "falsey" value 
(i.e. false, f, no, n or 0).
Expose a 'real' omnibus CLI!

A real grown-up CLI for Omnibus projects! Initially this will be used to
provide a "build" subcommand with "--no-timestamp" option which will be 
used in CI for release jobs.

Future enhancements include:

* A "create" subcommand that will allow easy skeletal project generation
* Possible elimination of Rakefile
* OMG! Ponies!
depend on latest stable Thor 0.17.0
Break-up method_option invocations.
use Mixlib::ShellOut to spawn rake process
Add a .gitignore file and remove the Gemfile.lock

It is an snit-pattern to check in the Gemfile.lock in gem repositories.
Merge branch 'cli'
Bump version to 0.5
redirect STDERR to STDOUT when running `omnibus build`
bump timeout to 2 hours on CLI subcommand shellout processes

10 minutes is *definitely not enough time to build chef-server! :)
Bump version to 0.5.1
cookbook compat fixes for Chef 11

Move the `runit` cookbook from `depends` to `suggests` in the git 
cookbook metadata as it is only required for the `git::server` which we 
don't use on Omnibus build slaves!
Bump version to 0.5.2
chef-11 attribute fix
Bump version to 0.5.3
prepare project for CI testing
relax Thor version constraint so Omnibus plays nicely with Berkshelf
OC-6037: Remove hard-coded msi package name and artifacts and allow paramterization
OC-6037: Fix missing iteration
Merge pull request #26 from opscode/adamed-oc-6037-omnibus-ruby-msi

OC-6037: Parameterize msi files for omnibus-chef and omnibus-pushy