Remove project push rules sync triggers after table migration
## Summary
Remove the DB sync triggers that keep `push_rules` and `project_push_rules` tables in sync for project push rules. These triggers are no longer needed after the application has fully migrated to read and write directly from the `project_push_rules` table.
## Background
As part of the [Cells 1.0 push rules restructuring](https://gitlab.com/groups/gitlab-org/-/epics/15534), project push rules were migrated from the shared `push_rules` table to the dedicated `project_push_rules` table. During the migration, DB sync triggers kept both tables in sync to allow safe rollback:
- `sync_project_push_rules_on_insert_update` - syncs inserts/updates from `push_rules` → `project_push_rules`
- `sync_project_push_rules_on_delete` - syncs deletes from `push_rules` → `project_push_rules`
## Note
Check [the implementation plan](https://gitlab.com/gitlab-org/gitlab/-/work_items/499156#implementation-plan-1) and make sure all previous steps have been completed before proceeding.
## Tasks
- [ ] Create migration to drop `sync_project_push_rules_on_insert_update` trigger and function
- [ ] Create migration to drop `sync_project_push_rules_on_delete` trigger and function
- [ ] Add specs for the migrations
## Dependencies
This issue should only be worked on after:
- `read_project_push_rules` FF is cleaned up
- `write_project_push_rules` FF is cleaned up
issue