Add database cookbook
remove s3backup template
Add database cookbook
remove s3backup template
regenerate latest metadata.json for consistency across cookbooks.
merge refactoring of the bootstrap->chef cookbooks
Generalizing database cookbook better, add node.save in mysql::server

* Search apps for user and db info
* create grants template
* remove aws specific part of recipe
* remove databag store of replication status because clients dont
  have admin access to create data bag items by default.
Update metadata across the board.
Database and application README updates.
require rubygems before calling Gem.clear_paths
require rubygems before calling Gem.clear_paths

If chef was not installed from rubygems, Gem may be uninitialized
constant because rubygems isn't loaded.
@node is deprecated, use node, chef commit f904589
COOK-316, add recipes to metadata for all cookbooks
Better integration of database and mysql cookbooks

* Don't try to manage same grants.sql anymore, database::master
will use 'app_grants.sql'
* app_grants.sql no longer manages the root, repl and debian-sys-maint
user grants, use what the mysql cookbook already has
* move mysql::server before the grants so its available before trying
to install
* mysql cookbook LWRP can now create databases
* database::master recipe will use the LWRP to create the database.
* Update README docs for above
move prune after unfreeze

frozen time should be as short as possible
ignore snapshot failure so that unfreeze happens

* second volume resource that prunes doesn't need all
the parameters repeated, they'll be used anyway.
bump metadata version for database publish to cookbooks site
[COOK-509] install packages/gems in execute phase
[COOK-511] CentOS/RHEL support for database cookbook
[COOK-512,COOK-397] mysql & database cookbook cleanup

* unnessesary number of platform specific templates
* use strings (vs symbols) for all node attribute keys
* mysql_database LWRP was leaking connections