chore: make mixin range interval configurable

[jmichalek132]

What this PR does / why we need it:

Address last recording rule which has a hardcoded range interval which is too small for scrape interval of 1m by making it configurable using existing variables.

Which issue(s) this PR fixes:
Fixes #13630

Special notes for your reviewer:

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• Title matches the required conventional commits format, see here
  • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
• Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
• For Helm chart changes bump the Helm chart version in production/helm/loki/Chart.yaml and update production/helm/loki/CHANGELOG.md and production/helm/loki/README.md. Example PR
• If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

[CLAassistant]

All committers have signed the CLA.

[cstyan]

hey @jmichalek132 thanks for this PR, but unfortunately right now this won't work as expected because we're still on an older version of the mixin-utils library that the histogram function is pulled from. The version we're on doesn't take in any parameter for the interval.

Can you run jb update and then generate the dashboards again?

[jmichalek132]

hey @jmichalek132 thanks for this PR, but unfortunately right now this won't work as expected because we're still on an older version of the mixin-utils library that the histogram function is pulled from. The version we're on doesn't take in any parameter for the interval.

Can you run jb update and then generate the dashboards again?

Yeah, sorry my bad I lost that change as I switched devices to work on the PR. Fixed now.

[cstyan]

@jmichalek132 thanks!