Enable addition of custom API and Engine TOML sections

[jkroll-deepgram]

Proposed changes

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

[bd-g]

While we’re at it, we should do this for both API and Engine. (We shouldn’t do for License proxy, fields aren’t added there on any sort of regular basis, so keeping it locked to a set of managed fields is reasonable IMO)

[bd-g]

Looks good!

We should add this parameter to the values.yaml file as well with an appropriate description so this option is properly documented, and then run helm docs to regenerate the README.

[jkroll-deepgram]

We should add this parameter to the values.yaml file as well with an appropriate description so this option is properly documented, and then run helm docs to regenerate the README.

Thanks @bd-g, done: 8b13dc0