The otomi-tasks for keycloak generates an incorrect well-known URL

[jeho]

Describe the bug: (a clear and concise description of what the bug is)

The otomi-tasks for keycloak generates an incorrect well-known URL

To Reproduce
Steps to reproduce the behavior:

1. Deploy Otomi with OIDC for Google
2. Observe that job-keycloak fails on obtaining data from the well-known url (HTTP 404)
3. Observe that task has build incorrect well-known URL by appending the /v2.0/ in the URI path

Expected behavior: (a clear and concise description of what you expected to happen)

Otomi tasks should not build the well-known url based on the oidc.issuer The well-known url should be given instead of the issuer.
Implement new interface, so users can define the oidc. wellKnownUrl in the values.

The otomi-tasks should receive the wellKnownUrl as env variable.

Legacy considerations:

If oidc. wellKnownUrl then it takes precedence over the oidc.issuer. Otherwise the legacy oidc.issuer is used.

Versions: (seen in console's /settings)

• Core Version 2.3.0