Warn if a background migration is finalized before the next planned required stop after it is introduced

It's desirable to have a pipeline tool that warns developers that a DB schema migration will potentially cause an upgrade stop for self-managed customers when introduced. It is even more desirable (probably required) to warn that an upgrade stop is being realized when schema migration is finalized, and remind developers that schema migration finalizations are only allowed for designated/planned upgrade stops unless there are urgent severe customer/security concerns.

With these warnings, we build another layer of defense to prevent unplanned/unexpected upgrade stops.

We introduced dictionary files to automatically finalize BBMs at the right time via housekeeper, and the plan was to long term also use them to detect if someone was finalizing early. It was dependent on a SSOT for upgrade stops, and we now have finalized the planned upgrades at .2, .5, .8, .11 that allows us to proceed to the DB tooling enhancement.

Deliverables

• A job fails or warning is added to migration testing if a finalization is introduced before the release following the next required stop
• There is a documented process and criteria for granting exceptions