Allow tenant specification in jsonnet ScaledObjects

[zalegrala]

What this PR does

Without this change, the ScaledObject created by enabling the autoscaling in the jsonnet expects to be able to query without a tenant. In environments which require a tenant for query, this becomes a challenge.

Here we include a config to allow the specification of a tenant, which when non-empty, will add the appropriate header during query to allow the Keda ScaledObject to query the needed metrics to make autoscaling decisions.

Which issue(s) this PR fixes or relates to

Fixes #

Checklist

• Tests updated.
• Documentation added.
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]. If changelog entry is not needed, please add the changelog-not-needed label to the PR.
• about-versioning.md updated with experimental features.

---

Note

Adds optional tenant setting to autoscaling ScaledObjects to send X-Scope-OrgID in Prometheus queries.

• Jsonnet autoscaling (operations/mimir/autoscaling.libsonnet):
  • Add _config.autoscaling_prometheus_tenant.
  • In KEDA Prometheus triggers, set customHeaders with X-Scope-OrgID=<tenant> when the config is non-empty.
• Changelog: Document the Jsonnet change to allow tenant configuration in ScaledObject metric queries.

^{Written by Cursor Bugbot for commit 893b49d. This will update automatically on new commits. Configure here.}