Add Settings migration for require SHA when merging
What does this MR do and why?
This MR adds migrations for a cascading settings column, to support SHA parameter requirement when using the merge API see: gitlab-org#20551+
This is being made configurable to not cause a breaking API change, and give users opportunity to opt-in.
References
https://gitlab.com/gitlab-org/gitlab/-/work_items/599954+
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.