Try to run the latest migration on start up if it is dirty (failed)

[IvanBelyakoff]

Problem

Currently there is no good way for user to recover if DB migration fails (besides restoring account, restoring DB from back up or manually fixing the DB issues). We dont support migration down (not sure if there is some technical limitation or we just dont use 'down' migration files.

What we could do is to try run the latest failed migration on startup. Then if we fix the migration issue in a new release (modify the buggy migration file), the issue will be fixed for the user.

Implementation

Try to run dirty migration on startup.

Acceptance Criteria

Write a test that migration proceeds successfully if the buggy migration file is fixed.