Cleanup `lazy_load_commits` feature flag

Summary

In #342497 (closed) we enabled the lazy_load_commits feature flag by default. This issue is to cleanup the lazy_load_commits feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.

Owners

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

Expectations

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.

Cleaning up the feature flag

• 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
  • /chatops run feature delete <feature-flag-name> --staging
  • /chatops run feature delete <feature-flag-name>
• Close this rollout issue.