Incorrect securityContext template references in API and Engine deployments

[trhynard]

What is the current behavior?

The API and Engine deployment templates incorrectly reference .Values.licenseProxy.securityContext instead of their respective component-specific security contexts (.Values.api.securityContext and .Values.engine.securityContext). Additionally, the documentation comments in the values.yaml file have misleading descriptions for the securityContext fields.

Steps to reproduce

1. Deploy the Deepgram self-hosted Helm chart with custom api.securityContext or engine.securityContext values
2. Inspect the deployed API or Engine pods
3. Notice that the pods are using the License Proxy's security context instead of their intended security contexts

Expected behavior

• API deployment should use .Values.api.securityContext
• Engine deployment should use .Values.engine.securityContext
• Documentation comments should correctly describe which component each securityContext applies to

Please tell us about your environment

• Operating System/Version: N/A
• Cloud Provider: AWS

Other information

This is a template reference bug in the Helm chart that affects security context configuration.