In v2.1 the ConfigMap should use resource.customizations key, please see https://medium.com/argo-project/argo-cd-v2-1-first-release-candidate-is-ready-c1aab7795638  post.

In the upcoming release, the resource.customizations key has been deprecated in favor of a separate ConfigMap key per resource. This allows to decompose the Argo CD configuration and makes it more convenient to use with config management tools such as Kustomize.

We should update Argocd Operator to generate the new resource customization key/value in argocd-cm as documented above.

Acceptance Criteria

• update gitops operator reconciler to generate resource customization config in the new format
• unit/e2e test and documentation
• fix propagated to gitops operator and cpaas midstream.
• tested and validated in cpaas built image