Kiali SSO fails when OIDC client is set to confidential

Bug

Description

If you supply Kiali with an OIDC client secret, the k8s resource is created properly but it is never consumed.
This results in a CODE_TO_TOKEN_ERROR failure from Keycloak when attempting to use a client set to confidential.
It seems as though the oidc-secret needs to be mounted in at /kiali-secret/oidc-secret as seen here

Steps to reproduce:

1. Configure Keycloak with a OIDC client configured as confidential.
2. Configure Kiali with the appropriate OIDC settings to use.
3. Attempt OIDC login. See failures in Keycloak server logs.
4. Change the client config to public
5. Attempt OIDC login. See successful auth.

BigBang Version

1.6.0