Add development notice in dev environments, with git SHA if it's easy to determine
Move SHA-finding code to lib, with tests
Change development notice to synchronous everything
Fix case sensitivity in recipient hash comparison

[fixes #501]

Previously the hash comparison was done on directly using the equality
operator. This proved to be too restrictive as hash implementations can
generate output of varying case. I changed the implementation so that
the generated hash and the expected hash are normalized to lowercase
before comparing.
Add test for lowercase hashes as well.
Fix test title
Merge pull request #502 from brianloveswords/501-case-insensitive-hashes

Fix case sensitivity in recipient hash comparison
Merge pull request #493 from stenington/dev-flag

Development notice
Use node 0.8 for travis tests.
Specify 0.8 in package.json [ci skip]
Adding VPAT page for Backpack 508 compliance
Merge pull request #528 from stenington/477-vpat

Adding VPAT page for Backpack 508 compliance
Initial integration with node-db-migrate.

This converts the CREATE TABLE code in lib/mysql.js to a migration
that can be rolled-back. Also added a test to ensure that it works.

Migrations are automatically run when the app is launched and when
the test database is set up at the beginning of each test. The latter
could get slow, but there are ways around it when that happens, such as
getting a mysqldump of the fully migrated state and executing it as a
series of SQL statements. But we'll cross that bridge if/when we come to it.
Added bin/db-migrate, which is a modified version of the db-migrate script.

I'm not a huge fan of this approach. Not only are we copy-pasting
code from db-migrate, thereby violating DRY, but the code uses undocumented
APIs which could break at any time. A better approach would be to
issue a pull request to node-db-migrate (or just use a fork) that
refactors it in a way that allows us to do what we need without
having to copy-paste the code. But figuring out how to do the refactoring
will take time, which we don't have much of right now.

Doing this also meant not calling createTables() in lib/mysql.js, i.e.
users need to run bin/db-migrate manually to ensure migration race
conditions don't occur between multiple server processes that are started
simultaneously.

I still need to:

* Document bin/db-migrate in the README, adding instructions on how to
  migrate up/down and create migrations.
* (optional) Add some code in app.js that checks to see whether we're
  at the latest migration, and report an error if not. This will be
  more helpful to developers than running code that expects a newer db
  schema and exploding confusingly.
Update default node installed by puppet to 0.8.19
Added VPAT point of contact
Added remarks for VPAT 1194.41 section and 1194.22l
Add VPAT link to footer
added 'start' target to makefile which does migrations, then runs up.
added section on Database Migrations to README.
Merge pull request #536 from stenington/puppet-node-0.8

Update default node installed by puppet to 0.8.19
Only use one worker when running up in development.