Update Sonar CRD to Consume OIDC Client Secret from Kubernetes Secrets

[zmotso]

Is your feature request related to a problem? Please describe.
The kind: Sonar Custom Resource Definition (CRD) currently includes sensitive data directly within its configuration under the OIDC section, specifically the sonar.auth.oidc.clientSecret.secured key. To enhance the security posture and align with Kubernete's best practices, it is essential to modify the Sonar CRD to consume the OIDC client secret from Kubernetes Secrets rather than storing it directly in the configuration. This change aims to secure sensitive information effectively by leveraging Kubernetes's native secret management capabilities.

Describe the solution you'd like
There is the possibility of setting up some secured Sonar settings from the Kubernetes Secret.

Describe alternatives you've considered
Set secured value directly in the Sonar CR.