Tidy up code and names for errors catalogue

[zenador]

What this PR does

Following what we've done in #2009, this PR changes MessageWithLimitConfig to accept multiple flags and adds 'tenant-' to one error ID.

Which issue(s) this PR fixes or relates to

N/A

Checklist

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

[56quarters]

I'm not sure it makes sense to add tenant- to each of the error IDs. The limits don't necessarily correspond to user-specific limits, they can also come from the limits section of the global configuration file: https://grafana.com/docs/mimir/latest/operators-guide/configuring/reference-configuration-parameters/#limits

[pracucci]

I'm not sure it makes sense to add tenant- to each of the error IDs. The limits don't necessarily correspond to user-specific limits, they can also come from the limits section of the global configuration file: https://grafana.com/docs/mimir/latest/operators-guide/configuring/reference-configuration-parameters/#limits

The tenant- prefix originated by a feedback I gave to Jeanette. After looking these changes, I want to step back. I agree with Nick that looks "too much". I think the only one where we need to clarify it is TooManyHAClusters, so I would add the tenant- prefix just to that. I think other errors have no need to disambiguate between per-tenant and per-instance (or per-something-else).

[pracucci]

Good job, LGTM!