Fixed a certificate mismatch that could crash-loop encrypted internal cache connections

The internal cache platform's operator sets one environment variable naming the trusted certificate authority for encrypted connections, but the shipped cache image's own startup script read a different, older variable name that the operator no longer sets - so enabling encryption produced an immediate crash loop ("tls-ca-cert-file wrong number of arguments") on the very first live instance, independent of any per-application configuration. Fixed at the shared chart level: the workaround is now applied automatically whenever encryption is turned on, so no future instance can hit this.