[k189] feat(metadata): introduce a separate split interval for recent query window

[grafanabot]

Backport 9e7725b from #11897

---

What this PR does / why we need it:

Metadata queries are split using a 24h interval by default. The same interval gets used in the cache key.
But it is not possible to extract a subset of labels/series from a cached extent, unlike samples they are not associated with a timestamp. To prevent short queries from returning the results of an entire 24h extent, caching is disabled for the last 24h by default using max_metadata_cache_freshness.

But we have noticed in our cloud environments that most queries fall in the last 24h interval. This pr introduces the following changes to help cache the recent metadata query results:

• Use a smaller split interval for caching recent metadata queries. Portion of the query within recent_metadata_query_window is split using a different interval of split_recent_metadata_queries_by_interval.
• Only use extents that are entirely within the requested metadata query range. This is done to avoid using extents that contain results from the outside of the requested range.

---

To use a shorter split interval for recent metadata queries, the following needs to be configured:

• recent_metadata_query_window to configure the window inside which the shorter split interval gets applied. Disabled by default.
• split_recent_metadata_queries_by_interval to configure the split interval for the portion of the query within the recent metadata query window. Defaults to 1h. Recommended to be configured to a value smaller than split_metadata_queries_by_interval.
• reduce max_metadata_cache_freshness to control the cache freshness

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• CHANGELOG.md updated
  • If the change is worth mentioning in the release notes, add add-to-release-notes label
• 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