Smart availability zones

[whites11]

What this PR does / why we need it

Towards: https://github.com/giantswarm/giantswarm/issues/30316

This PR makes 3 changes

• changes the helm chart to use a yaml file (in files/azs-in-region.yaml) to get a list of azs in a region when defaulting such value
• adds a go tool in the azs-getter folder to generate the above file automatically
• adds a github action that runs once a day the above tool and creates a PR if any change happens

this is to replace the previous logic that hardcoded "a", "b" and "c" as az name for each region

Checklist

• Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

[whites11]

A bit out of scope for this PR.
We provide the "autodetect region" feature as an helper, but we should error if we're unable to provide a sane default.

[whites11]

/run cluster-test-suites

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-aws-556-cluster-test-suiteshggqh
Commit SHA	dda6332
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

[github-actions]

There were no differences in the rendered Helm template.

Output

=== Differences when rendered with values file helm/cluster-aws/ci/test-mc-proxy-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-network-topology-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-wc-minimal-values.yaml ===

No difference

=== No differences at all ===

[calvix]

LGTM

[whites11]

skipping CI blocker. failures are in the deletion phase and being worked on.