docs: Update Loki components page with new bloom components

[chaudum]

What this PR does / why we need it:

The page was outdated and did not mention the new bloom planner and bloom builder components, but still mentioned the bloom compactor.

Checklist

• [x] Reviewed the CONTRIBUTING.md guide (required)
• [x] Documentation added
• [ ] Tests updated
• [x] 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

Signed-off-by: Christian Haudum christian.haudum@gmail.com

[loki-gh-app[bot]]

This PR must be merged before a backport PR will be created.

[loki-gh-app[bot]]

This PR must be merged before a backport PR will be created.

[chaudum]

@JStickler I removed the backport label for 3.0.x and 3.1.x, because these components are new. k218 will become the 3.2 release, so we should backport these changes to the respective branch.

[loki-gh-app[bot]]

This PR must be merged before a backport PR will be created.