feat(migrations): improve migration system

[samuelmasse]

Assures that the database version is persisted in a transaction that also contains any changes to the database schema. Tables are now created initially in a transaction all at the same time. Changes the status migration to create the table in the correct state after the migration has run (this is necessary to be future proof, in case a migration in the future needs to modify the schema again).

When adding a table, it is now required to add a migration (not only when modifying an existing table). This is required because not doing so might lead to problems in the future where running multiple migrations in a row could lead to corrupt database state, since a table that is needed does not exist in the expected format. We also can't allow the server to create its tables before running the migrations, because doing so could also lead to to problems in the future where a migration might expect to migrate a table as it was in a specific version but the server creates a table of a newer format that the migration doesn't expect.

Closes DEV-2216

[linear]

DEV-2216 Improve migration system

Comes from doing the migration in DEV-2205. We need to have a initial migration that creates all tables from the initial version of messaging. A migration needs to be added not only when a table is modified, but also when a table is added. In that case the migration creates the table as it was at that server version, and the down migration deletes the table.

When services register tables to be created, these should all be created afterwards at the same time using a transaction, and then the database version can be set (otherwise can lead to strange edge cases).

[laurentlp]

Small suggestions otherwise looks fine to me!