Description of the problem:
When importing a cluster in ACM that isn't an OCP cluster, its API server URL isn't populated as part of the `-cluster-secret`  that gets generated, hence when importing the cluster in Argocd using `GitOpsCluster` CR, the server URL isn't populated. 
Because of that, we cannot deploy an application using the ArgoCD integration to non-OCP clusters.

Release version:
2.4.2

Operator snapshot version:

OCP version:
4.9.23

Browser Info:
Firefox

Steps to reproduce:
1. Import an xKS cluster into ACM
2. Create a ManagedClusterSet, ManagedClusterSetBinding, GitOpsCluster and Placement CR to import clusters into ArgoCD
3. Add the label to match the Placement rule defined in previous steps to the imported xKS cluster

Actual results:
ArgoCD shows an empty server API URL in its cluster tab

Expected results:
ArgoCD to show the server API URL in its cluster tab

Additional info: