Startup warning due to missing Django migration for 'specify' app

[grantfitzsimmons]

Describe the bug
When starting a Docker container for recent versions of Specify 7, the logs show a warning indicating that the specify app has model changes that are not yet reflected in a migration file. The warning message is: Your models in app(s): 'specify' have changes that are not yet reflected in a migration, and so won't be applied.

This suggests that manage.py makemigrations was not run after the last model update before the Docker image was built.

To Reproduce
Steps to reproduce the behavior:

1. Start a Docker container using the v7.11.1 or v7.11.2 image.
2. Observe the container logs during the startup sequence.
3. The warning appears after the "Applying Django migrations" step.

Expected behavior
The application should start without any migration warnings. All model changes should be properly included in migration files as part of the development process before a new version is released.

Log Snippet
Here is the relevant portion of the startup log:

2025-09-24T16:03:09.346Z Running migrations:
2025-09-24T16:03:09.346Z   No migrations to apply.
2025-09-24T16:03:09.346Z   Your models in app(s): 'specify' have changes that are not yet reflected in a migration, and so won't be applied.
2025-09-24T16:03:09.346Z   Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

System Information

• Specify 7 Version: v7.11.1 (production release) and v7.11.2-prerelease / main

Additional context
This issue appears to be a regression, as it affects the latest production and pre-release versions. The fix is likely to run python manage.py makemigrations within the development environment and commit the resulting migration file(s) to the repository.

[acwhite211]

I think this is due to the PRs where we were moving files around in the back-end. Some of the migration files are not in the same Django apps anymore. I'll look into it some more.