Revert "Merge branch 'ghavenga-enforce-database-trigger-ff' into 'master'"

Purpose of revert

revert !208297 (merged) to resolve master broken in foss

• Wednesday 2025-11-12 16:02 UTC - `gitlab-org/gi... (gitlab-org/quality/engineering-productivity/master-broken-incidents#18860)
• !208297 (comment 2884483433)
• attempted fix: !212437 (closed)

Checklist

• Create an issue to reinstate the merge request and assign it to the author of the reverted merge request.
• If the revert is to resolve a broken 'master' incident, please read through the Responsibilities of the Broken master resolution DRI.
• [-] If the revert involves a database migration, please read through Deleting existing migrations.
• Add the appropriate labels before the MR is created. We can skip CI/CD jobs only if the labels are added before the CI/CD pipeline is created.

Milestone info

• I am reverting something in the current milestone. No changelog is needed, and I've added a ~"regression:*" label.
• I am reverting something in a different milestone. A changelog is needed, and I've removed the ~"regression:*" label.

Related issues and merge requests