Run migrations in order across repos - #4466

Some migrations in PostgreSQL implicitly depend on migrations in ClickHouse (there is at least one such migration), and because PostgreSQL migrations run first, they fail because from their point of view ClickHouse schemas are now "outdated":

How migrations were added (example):

• add table to PostgreSQL db
• add column to ClickHouse table
• run PostgreSQL data migration that reads from new column in ClickHouse

How migrations are run:

• run all Plausible.Repo migrations
• run all Plausible.IngestRepo migrations

Which results in this broken order:

• add table to PostgreSQL db
• run PostgreSQL data migration that reads from new column in ClickHouse <- fails
• add column to ClickHouse table <- never runs

It might be possible to run them in a single queue / order in db migrate command:

• collect all migrations to be run, order them by version / date
• start all repos (Repo, IngestRepo, ClickhouseRepo)
• execute them one by one