[Feature flag] Cleanup duo_include_context_file

Summary

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

• Feature flag has been globally enabled for 24 hours
  • Enabled 100% on production environment at 1:05 PM EST on 1/22/2025

• The feature flag will be removed completely.

Owners

• Team: Duo Chat
• Most appropriate slack channel to reach out to: #g_duo_chat
• Best individual to reach out to: @dillonwheeler
• PM: @tlinz

Stakeholders

• @dashaadu
• @ck3g - Best individual to reach for related Feature Flag
• #f_ai-context

Expectations

• Self Managed users will have the feature enabled on their instance after updating to 17.9

What might happen if this goes wrong?

N/A - All users on GitLab.com will already have the feature flag enabled.

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 <feature-flag-name> 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 <feature-flag-name> --dev --pre --staging --staging-ref --production
• Close this rollout issue.