This is an extension of GITOPS-1247

Although GITOPS-1247 fixed the initial issue (any Argo CD instance created by the openshift-gitops Argo CD would immediately be "out of sync"), the same behaviour happens once you set a new namespace to be managed by the new Argo CD.

Shorter version:

• Install OpenShift GitOps
• Use default Argo CD instance to create a new Argo CD insance (e.g developer-argocd)
• The "Application" in openshift-gitops should be green (in sync).  The new Argo CD instance (in developer-gitops) is ready for developers to use.
• A new namespace is created (e.g. developer-test) and it is labeled so that it is managed by "developer-gitops"
• A few seconds later, the "Application" in openshift-gitops that managed the developer Argo CD is now "out of sync" due to the new roles and bindings that the operator creates to manage that new namespace.

I've added some instructions to the end of my original test repo to show how to reproduce the issue.

https://github.com/pittar-sandbox/gitops-1247