Previously, we introduced an optional field in the GitOpsCluster CR to allow users to manually opt-in to the full, OLM-managed OpenShift GitOps operator on OCP clusters. Currently, if this field is not toggled, the addon defaults to the stripped-down, non-OLM version, even if the target cluster is capable of supporting the full experience. See https://issues.redhat.com/browse/ACM-26981 for more details.

We want to remove the need for manual configuration by making the GitOps addon "smart" enough to detect the target cluster's capabilities. The addon should automatically deploy the best possible version of the operator (OLM-managed) whenever the infrastructure supports it.

This will also help avoid issues such as: https://issues.redhat.com/browse/ACM-29934

where we are installing unnecessary resources into an OCP cluster.