GITOPS-11300: Document Argo CD Git request timeout

[nikitapal-12]

%23%23 Summary

• Document how to increase the Argo CD repo-server Git HTTP list-refs timeout (ARGOCD_GIT_REQUEST_TIMEOUT via spec.repo.env)
• Clarify that spec.repo.execTimeout is Helm/Kustomize only and that spec.extraConfig does not update argocd-cmd-params-cm

%23%23 Jira
https://issues.redhat.com/browse/GITOPS-11300

%23%23 Version(s)

• gitops-docs-1.22 (this PR)
• Please cherry-pick to gitops-docs-1.21 and gitops-docs-main

%23%23 Test plan

• Preview the Argo CD custom resource and component properties assembly
• Confirm the new Git request timeout procedure is nested under Repo server properties
• Confirm the YAML example uses spec.repo.env / ARGOCD_GIT_REQUEST_TIMEOUT
• Confirm docs warn not to edit argocd-cmd-params-cm or put the timeout in extraConfig

QE review:

• QE has approved this change.

[openshift-ci-robot]

@nikitapal-12: This pull request references GITOPS-11300 which is a valid jira issue.

Details

In response to this:

%23%23 Summary

• Document how to increase the Argo CD repo-server Git HTTP list-refs timeout (ARGOCD_GIT_REQUEST_TIMEOUT via spec.repo.env)
• Clarify that spec.repo.execTimeout is Helm/Kustomize only and that spec.extraConfig does not update argocd-cmd-params-cm

%23%23 Jira
https://issues.redhat.com/browse/GITOPS-11300

%23%23 Version(s)

• gitops-docs-1.22 (this PR)
• Please cherry-pick to gitops-docs-1.21 and gitops-docs-main

%23%23 Test plan

• Preview the Argo CD custom resource and component properties assembly
• Confirm the new Git request timeout procedure is nested under Repo server properties
• Confirm the YAML example uses spec.repo.env / ARGOCD_GIT_REQUEST_TIMEOUT
• Confirm docs warn not to edit argocd-cmd-params-cm or put the timeout in extraConfig

QE review:

• QE has approved this change.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @nikitapal-12. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.