setup scripts to deploy a new instance on heroku

This originated in the story formally known as "launch production instances" but I took it a different direction.
https://www.pivotaltracker.com/story/show/75724550

Instead I'm asserting that the current instances *are* the production instances and I launched the new staging instances, and seeded them with the current "production" database.

This pull request includes some useful scripts. Take a look @jmoody and @svevang.

They are predicated on having the following git remotes set up (so make sure you do this!)

```
$ git remote add production git@heroku.com:wetap.git
$ git remote add staging git@heroku.com:wetap-staging.git
$ git remote -v
origin  git@github.com:wetap/wetap-api.git (fetch)
origin  git@github.com:wetap/wetap-api.git (push)
production      git@heroku.com:wetap.git (fetch)
production      git@heroku.com:wetap.git (push)
staging git@heroku.com:wetap-staging.git (fetch)
staging git@heroku.com:wetap-staging.git (push)
```

NOTE that this bumps our monthly server bill up to $100/month. We can turn staging off once we're winding down development.