Description of problem:

Adding a self-signed TLS cert for the for the ApplicationSet Gitlab SCM Providerdoesn't work as expected in Gitops

Workaround:
Client have to use insecure=true in the ApplicationSet configs

Steps to Reproduce:
 
As described in [1] and validated with [2], the `scmRootCAConfigMap` must be set in the ArgoCD CR, e.g.:

spec:
  applicationSet:
    scmRootCAConfigMap: my-gitlab-scm-tls-cert

• The certificate is only mounted if the name of the scmRootCAConfigMap is “argocd-appset-gitlab-scm-tls-certs-cm”. 
• Then the certificate is created, but as a file in rootPath /app/tls/scm/cert/ with filename according to the key value in the CM. 

However, the openshift-gitops-applicationset-controller expects the certificate file as /app/tls/scm/cert and fails with:

level=error msg=“error reading certificate from file ‘/app/tls/scm/cert’, proceeding without custom rootCA : read /app/tls/scm/cert: is a directory”

[1] https://argocd-operator.readthedocs.io/en/latest/reference/argocd/#add-self-signed-tls-certificate-for-gitlab-scm-provider-to-applicationsets-controller

[2] https://github.com/argoproj-labs/argocd-operator/blob/b300521514289b1ae4fd9e4dd8fd23c5148a7164/tests/k8s/1-033_validate_applicationset_tls_scm_volume_mount/01-install.yaml

Prerequisites (if any, like setup, operators/versions):

OCP: 4.14.19
openshift-gitops-operator.v1.12.2