[Feature flag] Cleanup delayed_repository_update_mirror_worker

Summary

This issue is to cleanup the delayed_repository_update_mirror_worker feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.

Owners

• Team: groupsource code
• Most appropriate slack channel to reach out to: #g_create_source-code-be
• Best individual to reach out to: @vyaklushin

Stakeholders

Expectations

What might happen if this goes wrong?

Cleaning up the feature flag

• Create a merge request to remove delayed_repository_update_mirror_worker feature flag. Ask for review and merge it.
  • Remove all references to the feature flag from the codebase.
  • Remove the YAML definitions for the feature from the repository.
  • Create a changelog entry.
• Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post.
  • /chatops run auto_deploy status <merge-commit-of-cleanup-mr>
• Close the feature issue to indicate the feature will be released in the current milestone.
• If not already done, clean up the feature flag from all environments by running these chatops command in #production channel:
  • /chatops run feature delete delayed_repository_update_mirror_worker --dev
  • /chatops run feature delete delayed_repository_update_mirror_worker --staging
  • /chatops run feature delete delayed_repository_update_mirror_worker
• Close this rollout issue.