Controller does not refresh SDK client on secret name change (mTLS/API keys)

[Shivs11]

Is your feature request related to a problem? Please describe.

• Right now, the worker controller stores the mTLS secret's name as part of a cache key which it uses to understand if a temporal client needs to be refreshed or not.
• If one were to simply change the contents of the secret and not the secret name, the controller would not refresh the sdk Client and would simply use the cached one. This is wrong.

Describe the solution you'd like

• One idea

Additional context

[carlydf]

Problem: If someone changes their certificates long before expiry, we won't refresh their client and their calls to temporal will get permission denied errors, if the old certificate that the controller is using no longer has access.