Add zone awareness support for ingester

[SungJin1212]

This pull request introduces support for zone-aware ingester deployments in the Helm chart, allowing ingesters to be distributed across multiple availability zones (zones A, B, and C).

Which issue(s) this PR fixes:
Fixes #203

Checklist

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

[nschad]

I appreciate this but I don't really like this static config way. For example what if a customer has more than three zones? (for whatever reason)

What do you think @kd7lxl

This feels like just a whole lot of duped configs with a whole lot of pitfalls.

[kd7lxl]

Have you tried the technique in #203 (comment)

[SungJin1212]

@nschad @kd7lxl
Instead of hardcoding zone-a/b/c as separate keys, why don't you use a list like this?
Adding a 4th or 5th zone requires only a values.yaml change, no chart updates

zoneAwareness:
  zones:
    - name: zone-a
      replicas: 1
      nodeSelector: {}
    - name: zone-b
      replicas: 1
      nodeSelector: {}
    - name: zone-c
      replicas: 1
      nodeSelector: {}