Fitness function enforcing migrations for new/updated controllers

### What is this about?

Add a fitness function when a new controller is introduced and require a migration. This function would detect a new controller being added into the code repository and check for a migration change in the same PR. It would fail and allow the user to by-pass with a label or comment.

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [x] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

No files, tests, or entry points are named. Start by locating existing fitness functions and the conventions for detecting controllers, migrations, and PR labels or comments; done means a new or updated controller requires a migration change while supporting the described bypass.

Written by the indexing model from the issue text.