Update md5 checksum for cacert.pem

The certificate was updated as of 2014/04/22.
Lock down versions of all ChefDK's auxiliary gems

Currently when we create a build of ChefDK we get the latest released 
version of every auxiliary gem. This is dangerous at best. This change
locks down the versions.

I also wonder if we should just put these in the ChefDK gemspec OR 
Gemfile. If we decide to create `chef` subcommands that rely on any of
these tools as a library we'll have to (I'm thinking `chef lint`).
Merge pull request #176 from opscode/schisamo/lock-chefdk-auxiliary-gem-versions

Lock down versions of all ChefDK's auxiliary gems
Remove gecode from berks, use vendored gem instead
Add chef-vault to chefdk

* Creates chef-vault as a new software definition
* Adds chef-vault as a dependency of chefdk
* Add chef-vault to the appbundler list
laziness is a virtue unless copy/pasta

* libffi isn't a dependency of chef-vault.
Merge pull request #178 from jtimberman/jtimberman/chef-vault-definition

Add chef-vault to chefdk
typo, slashes and spaces are similar on my keyboard?
annnnd the gem built isnt in pkg/
Include kitchen-vagrant in default package
Bump kitchen-vagrant to 0.15.0 to include fix for kitchen-vagrant#70
Merge branch 'kitchen-vagrant'
Add sqitch and perl_pg_driver
Merge pull request #182 from opscode/jw/sqitch

Add sqitch and perl_pg_driver
Merge pull request #174 from gaffneyc/fix-cacerts-md5

Update md5 checksum for cacert.pem
Fix chefdk windows build issues
Add missing 'env' variable
Merge branch 'cm/perl_pg_driver'
The official remote for rebar is now rebar, not basho

Same tags should be there, but the rebar remote has more recent releases
that projects may wish to use via override (saving update of default
version for a later commit).
Add relx and up default_version of rebar to 2.2.0

relx provides more convenient Erlang project release generation, but
depends on rebar > 2.2.0 to we're upping the default rebar version to
the SHA of current HEAD.