[bitnami/keycloak] use hostname v2 options

[singhbaljit]

Description of the change

Use Hostname v2 options as v1 options are not used by default.

Benefits

Use updated configurations in alignment with upstream Keycloak project.

Possible drawbacks

Enabling hostname-strict when hostname is more secure, but may cause issues for some users.

Applicable issues

• fixes [binamit/keycloak] Helm chart using deprecated hostname v1 env variable #28586

Additional information

This has be merged after the image is updated, see bitnami/containers#70466.

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
• Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• All commits signed off and in agreement of Developer Certificate of Origin (DCO)

[djas19]

Keep in mind #28121 is still open/broken. I presume this change will have impact for some users as we don't fully control how hostnames/urls are constructed causing broken behaviour in setups with wildcards or path suffixes like httpRelativePath

[singhbaljit]

@djas19 this is only focusing on option name change, to avoid making this PR too complicated. proxy is deprecated anyways; so I think we should focus on removing it instead. I've opened a related issue as well, #28590.

[dgomezleon]

The changes LGTM. Just a couple of things:

• Bump a minor version (22.1.0) since it adds a new value
• Check DCO for all the commits

[singhbaljit]

Good catch, done and done. Waiting for bitnami/containers#70466...

[singhbaljit]

Rebased, and ready to merge