Implement a CI action that flags pull requests requiring migrations.

**Describe the usability problem**

We currently do not have the ability to flag whenever a PR needs migrations for a release. Sometimes this might lead to bugs when upgrading between app versions. As our team expands, it becomes essential to establish a streamlined process for automatically identifying PRs that require migrations, eliminating the need for manual effort.

**Screenshots**
_If applicable, add screenshots or links to help explain the issue_

**Proposed behavior**
There are many solutions to this but I propose we have CI checks for migrations:

### At the feature level:

After a new feature has undergone development, a CI check can be implemented to determine whether a ticket requires migrations.

OR
### At the release level:

Implementing a check during the process of cutting an RC to identify whether PRs require migrations or not. This additional step would help in accurately determining the migration needs associated with each PR.

Compare the proposed feature-level and release-level approaches, then inspect the repository's CI and release workflows to determine where such a check could run. Define how a pull request or release would be identified as requiring migrations and what passing or flagged output should look like; the issue does not name specific files or tests.

Written by the indexing model from the issue text.