With the new version of the openshift gitops operator, the openshift gitops operator manager launches a ArgoCD instance with default configurations.  This could override the ArgoCD instance with customized configurations launched by our ACM gitops addon.

Discussed with openshift gitops team, we will enhance the ACM gitops addon 

• Firstly let the openshift gitops operator manager launches a ArgoCD instance with default configurations. Then the ACM gitops addon controller will update the existing ArgoCD instance. This need to refactor the gitops addon controller to adopt the existing resources owned by openshift gitops operator previously. As such we will still organize and render openshift gitops operator and dependency mainfest by helm SDK, but we will apply/patch them without using helm SDK. 

We also noticed the argocd instance failed to be deployed on the Non-OCP clusters (tried in on EKS).  This requires some other changes including deploying additional dep CRDs.