Delete the merge_request_delete_gitaly_refs_in_batches feature flag

This feature flag was introduced in 16.3, which is more than 12 milestones ago.

As part of our process we want to ensure feature flags don't stay too long in the codebase.

Rollout issue: #416969

Remaining mentions of the feature flag (click to expand)

doc/user/project/repository/monorepos/troubleshooting.md
95:> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/416969) in GitLab 18.5. Feature flag `merge_request_delete_gitaly_refs_in_batches` removed.

Currently the feature flag is disabled on production

It is possible that this MR will still need some changes to remove references to the feature flag in the code. At the moment the gitlab-housekeeper is not always capable of removing all references so you must check the diff and pipeline failures to confirm if there are any issues. It is the responsibility of groupgitaly to push those changes to this branch.

Note: If you do not want to remove this feature flag at this time, you can add an intended_to_rollout_by_date attribute in the feature flag YAML file to prevent automated removal.

TODO for the reviewers before merging this MR

• See the status of the rollout by checking #416969, https://gitlab.com/gitlab-com/gl-infra/feature-flag-log/-/issues/?search=merge_request_delete_gitaly_refs_in_batches&sort=created_date&state=all&label_name%5B%5D=host%3A%3Agitlab.com
• Verify the feature flag status via chatops by running /chatops run feature get merge_request_delete_gitaly_refs_in_batches.
• Search for references to MergeRequestDeleteGitalyRefsInBatches in frontend part of code
• Search for references to merge_request_delete_gitaly_refs_in_batches in code
• Check if we need to remove any Gem or other related code by looking at the changes in !125333 (merged)

This change was generated by gitlab-housekeeper in CI using the Keeps::DeleteOldFeatureFlags keep.

To provide feedback on your experience with gitlab-housekeeper please create an issue with the label GitLab Housekeeper and consider pinging the author of this keep.