DB: Set revision to proper sha.

Since forgot-password-link was branched before the
projects to db branch was merged, alembic
complained that the migrations had diverged (due
to the branching).

This change sets it to the previous actual
revision set in production.
Password reset forms: Add CSRF token.

Since these forms aren't using ajax, it is
necessary to manually inject the token.
Emails: Place the reset link on a new line.

This just makes the email easier to parse and
quicker to find the reset link.
DB: Set revision to proper sha.

Since forgot-password-link was branched before the
projects to db branch was merged, alembic
complained that the migrations had diverged (due
to the branching).

This change sets it to the previous actual
revision set in production.
Password reset forms: Add CSRF token.

Since these forms aren't using ajax, it is
necessary to manually inject the token.
Emails: Place the reset link on a new line.

This just makes the email easier to parse and
quicker to find the reset link.
Merge hotfix-fix-password-migration (#107) into master

Fix forgot-password-link deployment.

There were a few things I missed when testing:
 * I had to fix the migration revision sha due to another branch
 * I had to add a CSRF token to the forms (since they don't use AJAX)

I also went ahead and put the reset link on a newline. I figured this
would make the e-mails a little easier to read.