Remove resource limits on Compose file templates

[bd-g]

Proposed changes

Resource limits can be an effective way to prevent containers from starving eachother.

However, in a single VM running multiple Deepgram containers (most common use case with Docker), allowing containers to have more ebb and flow in their resource usage can lead to greater performance and easier management.

This also prevents artificially low limits being enforced when these templates are used for more powerful instance types, but users forget to increase the default limits.

Types of changes

• 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)
  • Updated best practice on Compose templates

Checklist

• I have read the CONTRIBUTING doc
• I have tested my changes in my local self-hosted environment
• I have added necessary documentation (if appropriate)

[jkroll-deepgram]

Makes sense. Do we want to leave it commented-out, or document elsewhere how/when to impose resource limits? Or is that considered outside the scope of what we want to educate here?