Changes to migrations do not show in local tests while developement

[acostama]

Once a migration is written and ran for the first time any subsequent changes will not be applied by the SchemaMigrator. While this is done by design, it can propagate errors or require developers to manually cleanup tables to force SchemaMigrator to run the expected migrations. It would be beneficial to find a balance between making appropriate changes and re-running migrations each time.

[swankjesse]

We should build a checksum of schema migrations and store it in the DB. Then if the schema changes we can automatically fix.