[Feature flag] Rollout of `path_to_vulnerable_dependency`

Rollout & Remove the feature flag for Dependency Path - #227620 (closed)

What

Remove the :path_to_vulnerable_dependency feature flag ...

Owners

• Team: Secure
• Most appropriate slack channel to reach out to: #g_secure-composition-analysis
• Best individual to reach out to: @djadmin / @brytannia

Roll Out Steps

• Enable on staging
• Test on staging
• Ensure that documentation has been updated
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour
• Coordinate a time to enable the flag with #production and #g_delivery on slack.
• Announce on the issue an estimated time this will be enabled on GitLab.com
• Enable on GitLab.com by running chatops command in #production
• Cross post chatops slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel
• Announce on the issue that the flag has been enabled
• Remove feature flag and add changelog entry
• After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel

Testing

As per Roll Out steps, manual verification on the Staging environment. Unit testing would be written by the engineer to complement the implementation. SET has a testcase ticket - gitlab-org/quality/testcases#992 (closed) - to add an End to End test to verify on the regular Quality pipelines.