Story (Required)

• See parent epic and https://github.com/argoproj-labs/argocd-agent/issues/454 for a high level overview of why we are doing this.

Acceptance Criteria (Mandatory)

• Change the default argo cd agent install to require TLS from it's redis
  • When installing on OpenShift, if `.spec.argoCDAgent.principal` is defined, then we should automatically enable the `.spec.redis.autoTLS: "openshift"` configuration for that redis, and configure agent workloads to use the redis cert
  • Or, said another way, argocd agent setup should always use a secure redis.
  • For the non-OpenShift (Kubernetes) case – which is what the E2E tests run as – we should instead manually create a TLS Secret for Redis to use
• Update downstream OpenShift GitOps documentation as needed
• Update argocd-operator documentation as needed
• Unit/E2E tests to verify functionality