helm: build unique rollout-group names per chart release

[narqo]

What this PR does

This PR updates the helm chart, allowing Mimir's components to form a release scoped rollout groups, and not clash with any components, that aren't part of the release. That is if Mimir, Loki, Tempo are installed in the same namespace; or when multiple Mimir versions are installed in the namespace.

TODO I'm not yet sure how thse changes will affect the existing deployments. One needs to test this somehow.

Which issue(s) this PR fixes or relates to

Fixes #8406

Checklist

• Tests updated.
• Documentation added.
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
• about-versioning.md updated with experimental features.

[narqo]

TODO I'm not yet sure how thse changes will affect the existing deployments. One needs to test this somehow.

@lindeskar I don't believe I will get to extensive testing of this one in the near future, unfortunately. Maybe, if you have a testing stand, where you can verify that the changes here improve the problem you outlined in #8406 (and don't add more problems), this would be very helpful.

---

Update Also, a related discussion in Loki grafana/loki#13168 (comment) where folks mentioned why we don't want to support that.

[dimitarvdimitrov]

TODO I'm not yet sure how thse changes will affect the existing deployments. One needs to test this somehow.

yeah that's crucial to understand before merging this. I suspect the problem might come if an ingester is unavailable and then the rollout of this change happens - the rollout-operator might not take into account the unavailable ingester and roll out other zones too.

That at least one edge case I can think of