chore: [k211] chore: shard limited queries with a fixed sharding factor

[grafanabot]

Backport 6631c0f from #13576

---

What this PR does / why we need it:

We used to do this, it was removed during a change by accident.

the fixed shard factor approach here isn't the best but on really large label matchers if you do no sharding the subqueries can be too large for executing without any shards

Note: this does NOT actually limit the number of shards for the newer bounded shard calculations method, with this strategy the number of shards for limited query types will not be fixed.

Which issue(s) this PR fixes:
Fixes #

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