[bitnami/redis] Handle SIGTERM in kubectl-shared container

[kppullin]

Description of the change

When Redis Sentinel has the master service option enabled, the kubectl-shared container runs a script with an infinite while+sleep loop.

This script currently does not handle SIGTERM and causes the pod to hang upon termination until the terminationGracePeriodSeconds timeout elapses.

This change introduces a preStop hack to create a terminate file, which is used as a signal to the script that it should exit the infinite loop.

Possible drawbacks

No known drawbacks

Applicable issues

N/A

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• 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)

[carrodher]

Thanks for your contribution! Please submit changes to multiple charts in separate PRs to facilitate automated testing and merge of pull requests.

[kppullin]

Thanks @carrodher . I've removed the valkey changes.

[carrodher]

Unfortunately, there is still one more thing... Your fork doesn't allow @bitnami-bot to access it as a maintainer, which is required for the GitHub Action in charge of automatically updating the README, CHANGELOG, etc to succeed.

remote: Permission to iherbllc/bitnami-charts.git denied to bitnami-bot.
fatal: unable to access 'https://github.com/iherbllc/bitnami-charts/': The requested URL returned error: 403
Error: Process completed with exit code 128.

Could you please check this?

[kppullin]

@carrodher I've granted bitnami-bot access to the repo, however the invitation is pending and the pipeline still fails. Not sure what else I can do from my end.