refactor(blooms): Apply retention in planner

[salvacorts]

What this PR does / why we need it:
This PR implements retention in the bloom planner.

Notes to reviewers

The retention manager is copied from the bloom compactor, the only difference is that we have removed the logic to check if the compactor owns the retention by looking at the ring.

Therefore I'd focus on reviewing:

• Docs
• Config.go
• Metrics.go
• Planner.go
• Skim over retention.go and retention_test.go

Tested out in dev by setting the retention_period: 10d for tenant 145265.

Before retention: Both tenants have blocks up to the earliest day built.

After retention: Tenant 29 still has data for older days but 145265 don't.

Here are the retention logs:

2024-07-11 12:06:09.624	level=info ts=2024-07-11T10:06:09.546039726Z caller=retention.go:179 component=bloom-planner subcomponent=retention-manager msg="finished applying retention" daysProcessed=6 tenants=1
2024-07-11 12:06:02.124	level=info ts=2024-07-11T10:06:02.073912794Z caller=retention.go:156 component=bloom-planner subcomponent=retention-manager day=2024-06-25 tenant=145265 msg="applying retention to tenant" keys=259
2024-07-11 12:05:54.525	level=info ts=2024-07-11T10:05:54.455099907Z caller=retention.go:156 component=bloom-planner subcomponent=retention-manager day=2024-06-26 tenant=145265 msg="applying retention to tenant" keys=259
2024-07-11 12:05:46.724	level=info ts=2024-07-11T10:05:46.6384181Z caller=retention.go:156 component=bloom-planner subcomponent=retention-manager day=2024-06-27 tenant=145265 msg="applying retention to tenant" keys=259
2024-07-11 12:05:38.624	level=info ts=2024-07-11T10:05:38.618366406Z caller=retention.go:156 component=bloom-planner subcomponent=retention-manager day=2024-06-28 tenant=145265 msg="applying retention to tenant" keys=259
2024-07-11 12:05:30.424	level=info ts=2024-07-11T10:05:30.420296936Z caller=retention.go:156 component=bloom-planner subcomponent=retention-manager day=2024-06-29 tenant=145265 msg="applying retention to tenant" keys=259
2024-07-11 12:05:21.824	level=info ts=2024-07-11T10:05:21.749845286Z caller=retention.go:156 component=bloom-planner subcomponent=retention-manager day=2024-06-30 tenant=145265 msg="applying retention to tenant" keys=257
2024-07-11 12:05:21.325	level=info ts=2024-07-11T10:05:21.270021915Z caller=retention.go:92 component=bloom-planner subcomponent=retention-manager msg="Applying retention" today=2024-07-11 lastDayRun=1970-01-01

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

[chaudum]

Can we hide this setting from the docs? Usually you don't need to set this, only in very special edge cases.

[chaudum]

Because it can cause confusion and could be mixed up with retention period of blooms, which it isn't right?

[salvacorts]

I don't have an strong opinion on this. I'll go ahead and hide it.