Upgrade database migrations

[No767]

Summary

This PR focuses on completely rewriting the database migrations to an newer home-grown system. This system will possibly break the existing migrations and data, so this PR is reviewed very heavily.

The rationale here is to centralize all migrations code to an home-grown solution as asyncpg-trek has many issues that made it harder to detect and identify files for particular features. This new system is based off of R. Danny's migrations runner.

Caution

This PR may break the internal code of Catherine-Chan

Types of changes

What types of changes does your code introduce to Catherine-Chan
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (Updates to README.md, the documentation, etc)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes. (if appropriate)
• All workflows (except pre-commit.ci) pass with my new changes
• This PR does not address a duplicate issue or PR

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud