[Feature flag] Rollout of `ci_fix_commit_status_retried`

What

Remove the :ci_fix_commit_status_retried feature flag ...

Introduced in: !54300 (merged).

Owners

• Team: grouppipeline authoring
• Most appropriate slack channel to reach out to: #g_pipeline-authoring
• Best individual to reach out to: @furkanayhan

Expectations

What are we expecting to happen?

• We start to update older commit-statuses if it is tried to be retried via API.
• We start to update older commit-statuses if it is a pages:deploy job and retried.

What might happen if this goes wrong?

UPDATE query may fail at worst... Or may take long...

What can we monitor to detect problems with this?

• We should not see an increase of "500" response => https://log.gprd.gitlab.net/goto/c972a59852d5e12ce10593159a071acf
• We should not see an increase of response time average => https://log.gprd.gitlab.net/goto/ab081ea275df6277cd7a475ffae03b1f
• We should not see an increase of "fail" job status => https://log.gprd.gitlab.net/goto/cecdc414bf68ddb9176d617da04c0f18
• We should not see an increase of duration average => https://log.gprd.gitlab.net/goto/ab0e13ef0f390bb614dd1a6117cb064c

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

• gitlab-org/gitlab project
• gitlab-org/gitlab-com groups
• ...

Roll Out Steps

• Enable on staging (/chatops run feature set feature_name true --staging)
• Test on staging
• Ensure that documentation has been updated
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=gitlab-org/gitlab feature_name true)
• Coordinate a time to enable the flag with the SRE oncall and release managers
  • In #production mention @sre-oncall and @release-managers. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
• Announce on the issue an estimated time this will be enabled on GitLab.com
• Enable on GitLab.com by running chatops command in #production (/chatops run feature set feature_name true)
• 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. Ensure that the feature flag definition YAML file has been removed in the same MR that is removing the feature flag from the code
• After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel

Rollback Steps

• This feature can be disabled by running the following Chatops command:

/chatops run feature set --project=gitlab-org/gitlab feature_name false