[bitnami/redis] fix: update JSON schema to allow string values for values passed to tpl

[piccit]

Description of the change

Updates all properties in values.schema.json that are directly passed to tpl to also allow for string fields.

Benefits

Fixes schema to allow passing strings to tpl for all values that are template-able

Possible drawbacks

None

Applicable issues

• fixes [bitnami/redis] json schema too strict for any template-able value #29451

Additional information

None

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)

[jotamartos]

Thank you for taking the time to contribute but I can approve this change, sorry. There are many parameters from there that do not support a simple string to configure them (hostAliases, customLivenessProbe, customRedinessProbe, extraEnvVars, ...). As you can see, those are objects/arrays that you need to define in the values.yaml file when deploying the solution.

[piccit]

There are many parameters from there that do not support a simple string to configure them (hostAliases, customLivenessProbe, customRedinessProbe, extraEnvVars, ...). As you can see, those are objects/arrays that you need to define in the values.yaml file when deploying the solution.

@jotamartos No, that's not true - per the issue #29451 and related #27319 and PR #27441 anything that is passed to the template function(s) can accept a string. Having the schema enforce not-string breaks the ability to utilize the template (see example in #29451.

[piccit]

Bump @jotamartos, please re-open and re-review per the linked issues and pr

[jotamartos]

Sorry for the late reply here. I've checked the issues you shared and you are completely right. It's important to take into account what @migruiz4 mentioned in #27441 but all in all this PR is completely legit. Please bump the branch and update the version so I merge the changes.

[jotamartos]

Update: I could resolve the conflicts using the UI and the changelog will be automatically generated soon. If tests pass, I'll merge the changes