feat: implement skipping migrations if no new migration files

[lethanhdat762003]

What?

• Skipping migrations when no new migration files found

Why?

• To optimize development productivity

How?

• By adding a new table in public schema. And from that, detect if there's any new migrations files. If yes, run the migrations. Else, skipping migration phase.

Metric	Before	After
Migrations run per day	50 tenants × 5 restarts = 250 migration scans	5 restarts × 1 hash check = 5 hash checks (+ 50 on the 1 day a migration ships)
Time wasted per day	250 × 0.6s = 150s	5 × 0.01s = 0.05s
DB queries per day	250 × (1 + tenants) = 12,750	~10

Testing?

• Functional Testing
• Security
• Performance
• Error Handling
• Code Quality
• Documentation
• Database
• Deployment
• Final Review

Anything Else?

[gemini-code-assist]

Code Review

This pull request updates the Docker entrypoint to use a custom 'migrate_smart' command instead of standard Django migrations, and adds the 'common' package to INSTALLED_APPS in settings.py. However, adding the parent 'common' package directly alongside its sub-packages is discouraged in Django as it can lead to app label conflicts and double model registration. It is recommended to register only a specific sub-app containing the migration command instead.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.