[DevOps]: Squash database migration files before production deployment

### Task Details

Many database migration files were generated over the course of the beta development period. These include schemas that were refactored, with fields and relationships added or removed based on stakeholder feedback.

Before deploying the production build at NERSC, we should squash the migration files into a single migration to ensure a clean baseline for future changes.

### Steps to Complete

TBD

### Additional Notes

_No response_

Start by locating the database migration files and the production deployment configuration for NERSC. Review the migration history to determine the current schema baseline and confirm how migrations are applied during deployment. Done means the beta migration history is safely replaced by one migration that represents the production schema and future migrations can build on it.

Written by the indexing model from the issue text.