Rollout `lazy_load_commits` feature flag

Summary

This issue is to rollout the feature on production, that is currently behind the lazy_load_commits feature flag.

Owners

• Team: groupsource code
• Most appropriate slack channel to reach out to: #g_create_source-code
• Best individual to reach out to: @jerasmus

Expectations

What are we expecting to happen?

Logs tree (commit data) should lazy load on the repository files list.

What might happen if this goes wrong?

Commit data won't load on the repository files list.

Rollout Steps

Rollout on non-production environments

• Enable the feature globally on non-production environments.
  • /chatops run feature set lazy_load_commits true --dev
  • /chatops run feature set lazy_load_commits true --staging
• Verify that the feature works as expected. Posting the QA result in this issue is preferable.

Specific rollout on production

• Ensure that the feature MRs have been deployed to both production and canary.
  • /chatops run auto_deploy status <merge-commit-of-your-feature>
• If you're using project-actor, you must enable the feature on these entries:
  • /chatops run feature set --project=gitlab-org/gitlab lazy_load_commits true
  • /chatops run feature set --project=gitlab-org/gitlab-foss lazy_load_commits true
  • /chatops run feature set --project=gitlab-com/www-gitlab-com lazy_load_commits true
• Verify that the feature works on the specific entries. Posting the QA result in this issue is preferable.

Preparation before global rollout

• Check if the feature flag change needs to be accompanied with a change management issue. Cross link the issue here if it does.
• Ensure that you or a representative in development can be available for at least 2 hours after feature flag updates in production. If a different developer will be covering, or an exception is needed, please inform the oncall SRE by using the @sre-oncall Slack alias.
• If the feature might impact the user experience, notify #support_gitlab-com and your team channel (more guidance when this is necessary in the dev docs).

Global rollout on production

All /chatops commands that target production should be done in the #production slack channel for visibility.

• Incrementally roll out the feature.
  • Enable the feature globally on production environment.
    • /chatops run feature set lazy_load_commits true
• Announce on the feature issue that the feature has been globally enabled.
• Wait for at least one day for the verification term.

Release the feature

Feature flag has been enabled by default, cleanup will be done in a follow-up

Rollback Steps

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

/chatops run feature set <feature-flag-name> false