[argo-cd] Allow for specifying Certificate Authority as Secret and have it be trusted by the installation

[rgarcia6520]

Is your feature request related to a problem?

When setting up SSO pointing to an internal OIDC host the pods state they cannot complete the connection and do not trust the certificate.

We are currently performing this workaround showed here however several of the other helm-charts we deploy and configure allow for specifying a certificate authority as a secret and getting auto-mounted into the pods.

Related helm chart

argo-cd

Describe the solution you'd like

The ability to have a value (global or otherwise) to list an array of kubernetes secrets which get mounted into /etc/ssl/certs/ on the pods and therefore trusted by the installation.

Describe alternatives you've considered

Currently using this workaround showed here but would be nice for the chart to handle these on the backend

Additional context

No response