Support removing resource limits on engine pods

[brianrudolf]

Proposed changes

Allow null or an empty string to be set for the engine CPU and memory limits to avoid setting limits on these containers.

Resolves #92

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
  • Tested by deploying from local chart, upgrading from a previously deployed chart.
  • Values files updated to set:

engine:
 resources:
   limits:
     cpu: null
     memory: ""

• helm diff output

         resources:
           requests:
             memory: "20Gi"
             cpu: "6"
             nvidia.com/gpu: 1
           limits:
-             memory: "40Gi"
-             cpu: "8000m"
             nvidia.com/gpu: 1

• I have added necessary documentation (if appropriate)
  • I ran helm-docs locally but there was no change

Further comments

[jkroll-deepgram]

@brianrudolf thanks for the contribution!