Rename project_versions table to project_commits - #47085

NOTE for future table renames: dashboard table renames will cause shared tests in the test environment to fail due to the new table not existing in dashboard_test1. We use dashboard_test1 for pegasus/lib etc tests so that it doesn’t muddy up dashboard_test which is used for UI tests. However, dashboard_test1 (through dashboard_test16) are setup by the step that runs dashboard unit tests. In order for dashboard_test1-16 to be migrated, dashboard tests need to be manually run in test first. Once dashboard tests have been manually run in the test env, restart the test build.

More context in #47038

Rename db table project_versions to project_commits and update references to the table.

The rename migration also includes the creation of a db view with the old table name so that in the time between when the migration is run and the app code deploys the code referencing the old table name will still return data

Links

• jira ticket: LP-2415

Testing

• Tested that committing and viewing commits works after the migration
• Tested that after running the migration, before updating the code references, committing and loading commits still worked

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked