[bitnami/vault] Parametize caBundle in mutatingwebhook

[tspiri26]

Description of the change

We have a cluster with multiple Vaults, each located in a different namespace. ArgoCD attempts to apply the caBundle with an empty string as its value. However, the cluster automatically populates the caBundle with a certificate, causing ArgoCD to fail when it tries to reapply the object with the empty string value.

Benefits

Mentioned above.

Possible drawbacks

N/A

Applicable issues

N/A

Additional information

N/A

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)