feat: add topologySpreadConstraints values

[ron-damon]

What issues does your PR fix?

• Resolves Add support for topologySpreadConstraints to Helm Chart #581

What does your PR do?

This PR adds the following values:

• airflow.defaultTopologySpreadConstraints (default: [])
• airflow.kubernetesPodTemplate.topologySpreadConstraints (default: [])
• airflow.dbMigrations.topologySpreadConstraints (default: [])
• airflow.sync.topologySpreadConstraints (default: [])
• scheduler.topologySpreadConstraints (default: [])
• web.topologySpreadConstraints (default: [])
• workers.topologySpreadConstraints (default: [])
• triggerer.topologySpreadConstraints (default: [])
• flower.topologySpreadConstraints (default: [])
• pgbouncer.topologySpreadConstraints (default: [])

Checklist

For all Pull Requests

• Commits are signed off
• Commits have semantic messages
• Documentation updated
• Passes ct linting

[MrBones757]

Awesome to see a PR for this - I'm looking for this myself and was going to submit a PR for it if there wasn't already one
What is the status of this PR? is there an eta on seeing this released / is there any additional testing / work required on this feature?

Happy to help where needed.
Thanks in advance!

[stale]

This issue has been automatically marked as stale because it has not had activity in 60 days.
It will be closed in 7 days if no further activity occurs.

Thank you for your contributions.

---

Issues never become stale if any of the following is true:

1. they are added to a Project
2. they are added to a Milestone
3. they have the lifecycle/frozen label

[ron-damon]

/remove-lifecycle stale

[saschajullmann]

Hey all,

is there any timeline here/ is there anything you need help with in order to allow this to get merged @thesuperzapper ?

[jbvaningen]

We would also love to have this PR merged! This is currently one of the main blockers for us to avoid monkey-patching the chart in our Airflow setup

[stale]

This issue has been automatically marked as stale because it has not had activity in 60 days.
It will be closed in 7 days if no further activity occurs.

Thank you for your contributions.

---

Issues never become stale if any of the following is true:

1. they are added to a Project
2. they are added to a Milestone
3. they have the lifecycle/frozen label

[ron-damon]

/remove-lifecycle stale

[thesuperzapper]

@ron-damon thanks for your great work on this!

I pushed a small cleanup to re-order the values and update the docs pages.

It will be in the next release of the chart.