Fixing Deployments off Master with 0.0.56

We had to make changes to a migrator in the 0.0.56 release. If you've only ever deployed full releases you should be fine, but if you've deployed a version of Magda that you build from code after the 0.0.55 release but before 0.0.56, you might have the problem of the registry migrator failing, because flyway really doesn't like its migrators getting changed.

To fix it:

1. Use kubectl port-forward to connect to your DB (NOT the migrator pod)
2. Go to the magda-migrator-registry-db directory in a command line, and run

../magda-db-migrator/flyway-4.2.0/flyway repair -baselineOnMigrate=true -url=jdbc:postgresql://localhost/postgres -locations=filesystem:sql -user=${PGUSER:-postgres} -password=${PGPASSWORD}

Swap the user and password values with those that work for your database.

This should fix up the flyway tables and allow the migration to work.