Recreate all migrations for django 2.2 upgrade.

[Cryptophobia]

We upgrade to django 2.2 in #141 .

We can now recreate the migration files for django 2.2 to make sure migrations can be smooth process going forward.

[pasanchamikara]

Is this still an open issue? @Cryptophobia , Would it be okay if I work on it

[pasanchamikara]

Appears migrations are up-to date, could be closed

[Cryptophobia]

Hi @pasanchamikara ! Nice to meet you.

The idea of this story is to clear all the migrations into one initial file since we haven't been upgrading or changing the API in quite a few versions now. Everyone using Hephy should already be running the latest Django schema version and we don't really need these migrations for all of our running databases. We can clear them all down into one initial migration file and in the future start going forward with new migrations?

Also we have images that exists with old migrations so if anyone requires them, they can just pull an older version of docker controller image and run it on their cluster to upgrade their database. Then they will continue using new images without the migrations going forward.

I think we just want to do Scenario #2 outlined here: https://simpleisbetterthancomplex.com/tutorial/2016/07/26/how-to-reset-migrations.html

If you have experience in Django or not, it looks like a pretty easy process, we just haven't gotten around to doing this. But you would need to spin up local postgresql database outlined here so that we can be sure it all works correctly without the migrations: #110 (comment)

I would be happy to approve a PR.

[pasanchamikara]

@Cryptophobia thank you for your kind response. Created the PR for you to review #154