Enable co-existence of Centralized (Push) and Agent-based (Pull) deployment models within the same Argo CD Control Plane.

With the introduction of the Argo CD Agent in OpenShift GitOps 1.19, customers can now utilize a "Pull" architecture. However, current architectural constraints prevent a single Argo CD instance from managing clusters via both the standard "Push" model (connecting to the remote cluster API) and the "Pull" model (Agent-based) simultaneously.

This request is to enable a hybrid mode where a single OpenShift GitOps control plane can manage a mixed fleet of clusters; some connected via the standard centralized controller and others via the Argo CD Agent.

Business Requirements:

• Licensing Constraints: The Argo CD Agent feature is currently supported/available only on specific top-tier subscriptions (OCP+).

• Operational Efficiency: The customer requires a central control plane to manage their entire estate. Segregating the control planes based on deployment methods (one instance for "Push" clusters, another for "Pull" clusters) introduces significant operational overhead, infrastructure duplication, and complexity in managing Day 2 operations.

• Flexibility: As the customer adopts the Agent for scale in certain network segments, they need to maintain legacy or lower-tier clusters on the standard Push model without fracturing their GitOps management structure.