Add check to ensure that migration on PR isn't outdated

[Eddasol]

Describe the improvement you would like to see
If a PR (B) with a migration is rebased on a commit (A) that also has migrations, the migrations (for B) needs to be regenerated. If not this will create problems for the next PR that includes migrations.

There should be a way to warn such that the chance of taking in outdated migrations are reduced.

One suggestion is to have a workflow that autogenerates the migrations for the PR and checks if it matches the migrations that is included in the PR. In some cases its necessary to manually change a migration so such a check should only be a warning and not a blocker.

Alternativ is to check if timestamp of included migration is newer that previous migration

How will this change existing functionality?

How will this improvement affect the current Threat Model?

[github-actions]

This issue has been automatically marked as stale due to inactivity.

[Christdej]

Look at sara for a way to solve this