[Feature flag] Cleanup container_scanning_continuous_vulnerability_scans

Summary

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

Owners

• Team: groupcomposition analysis
• Most appropriate slack channel to reach out to: #g_secure-composition-analysis
• Best individual to reach out to: @hacks4oats
• PM: @johncrowley

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 container_scanning_continuous_vulnerability_scans 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 e83cca1bc71aad2ed62bdd56b315265f1170a325
• 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 container_scanning_continuous_vulnerability_scans --dev --pre --staging --staging-ref --production
• Update the documentation to reflect the feature flag removal in the history, and create a release post.
  • Updated in !150593 (merged)
  • Create a release post
• Close this rollout issue.