[Feature flag] Cleanup blame_ignore_revs

Summary

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

Owners

• Most appropriate Slack channel to reach out to: #g_create_source-code
• Best individual to reach out to: @j.seto

Stakeholders

Expectations

What might happen if this goes wrong?

Cleaning up the feature flag

• Specify in the issue description if this feature will be removed completely or will be productized as part of the Feature Flag cleanup
• Create a merge request to remove blame_ignore_revs 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 42f6c937a046f879171be2163d7795d4b7ec689c
• 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 blame_ignore_revs --dev --pre --staging --staging-ref --production
• Close this rollout issue.