Add topologySpreadConstraints field to Helm chart.

[hongyiweiwu01]

Proposed changes

This PR adds the topologySpreadConstraints field to the deployment template for the API, engine, and license proxy pods. This field allows us to evenly distribute the pods from the same deployment across availability zones, among other criteria.

Types of changes

What types of changes does your code introduce to the Deepgram self-hosted resources?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update or tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have tested my changes in my local self-hosted environment
  • Please describe your testing setup and methodology here
• I have added necessary documentation (if appropriate)

Further comments

[pcgeek86]

Thanks for submitting this pull request @hongyiweiwu01! We appreciate you taking the time to do that.

We will take a look and see if we can merge this. We will need to test it and ensure that it does not cause any disruption to our existing self-hosted deployment process for all of our customers.

[jkroll-deepgram]

Thanks @hongyiweiwu01 for the contribution! This change will go out in a future chart release within the next week or so.