The temporal scaler now always attaches the temporal-namespace header on requests to the temporal server. Previously, this header was only set (at the keda scaler) level on requests when the scaler metadata contained an api key.

Note that namespace specific gRPC requests already contained the temporal-namespace header on every request, but the initial GetSystemInfo request does not, because it is not a namespace specific request: temporalio/sdk-go#1458

Checklist

• When introducing a new scaler, I agree with the scaling governance policy
• I have verified that my change is according to the deprecations & breaking changes policy
• Tests have been added
• Changelog has been updated and is aligned with our changelog requirements
• A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
• A PR is opened to update the documentation on (repo) (if applicable)
• Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #7079

I don't believe that any documentation needs to be updated, since there is no mention of the temporal-namespace header on the current scaler documentation, but please correct me if I should add to the documentation.

For potential tests, I could do two things:

• Create a new method getTemporalClientDialOptions that returns all of the dialOptions, update getTemporalClient to call that method, and then assert that the interceptor is always added
• Add an in-memory gRPC temporal server, and validate that requests from the scaler to the in memory server always contain the expected header in unit tests