Find a way to prevent coupling future migrations with business domain code by mistake

Most of the migrations define their own models to avoid importing from the rest of the source code, but as seen in https://github.com/hypothesis/h/issues/8541, it is possible to make a mistake.

It would be useful to have some automated way to highlight when a migration is importing business domain code, as this is usually an overlook.

One option is a linting rule. This package seems to go in that direction https://pypi.org/project/import-linter/, but it would be good to be able to do this with the existing tooling.