Primisify createSchema() ready for migration patches
Automatically update the database when a new patch level is required

We don't automatically downgrade the database for previous patch
levels since that could be dangerous. Instead, any reverse patches
should be applied manually.
Add a bin/db_patcher.js script, run it with start-local.sh
Make sure bin/key_server.js checks what the db patch level is
Minor tweaks from review of Issue #494
Merge pull request #643 from chilts/issue-494-db-migration-strategy

Issue 494 db migration strategy
Run the db_patcher.js script after each deploy
jshint; ignore stdout from key_server pipeline in the start scripts
Exit key_server when stdout is piped and the other process exits

This handles the case where notifier.js crashes. We need
both processes to be running so when one exits the other
needs to in order for the process manager to restart the
script.
better mysql connection error handling
train-07
resend blackout period
Add a call to /session/status in the loadtest
Merge pull request #654 from dannycoates/t07-a

resend blackout period
set the resendBlackoutPeriod to 0 in dev.json
Merge pull request #652 from mozilla/rfk/session-status-in-loadtest

Add a call to /session/status in the loadtest
Adding grunt validate-shrinkwrap task to npm postinstall script
Merge pull request #658 from pdehaan/issue-617-shrinkwrap2

Adding grunt validate-shrinkwrap task to npm postinstall script
Moving grunt validate-shrinkwrap from npm postinstall to Travis
Merge pull request #659 from pdehaan/travis-shrinkwrap

Moving grunt validate-shrinkwrap from npm postinstall to Travis