Add Flux max_streams Engine setting to Helm chart

[pcgeek86]

Proposed changes

• Adds the flux.max_streams configuration to the Deepgram engine.toml for Helm deployments for Kubernetes clusters

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

[jkroll-deepgram]

@pcgeek86 I added one comment. Additionally, to pass CI, please add a line under Unreleased in the changelog (here), something like:

## Unreleased

### Added

- Exposed `flux.max_streams` value for Flux capacity management

[jkroll-deepgram]

Can you please stub this out for license_proxy_deploy/engine.toml too?

self-hosted-resources/common/license_proxy_deploy/engine.toml

Lines 60 to 62 in 5a1f793

	### Enable Flux turn-based streaming STT
	[flux]
	enabled = false # or true