docs: update resource entry comments for CPU limits and production recs

[natemollica-nm]

---

Changes proposed in this PR

• Updates the values.yaml comment documentation to recommend setting CPU limits to null in production for service-mesh–related components (e.g., connectInject, meshGateway, terminatingGateway, API Gateway, etc.).
• Adds references to the recommended CPU and memory guidelines (Small vs. Large clusters) for Consul servers in production, as per the reference architecture.

How I've tested this PR

• Verified that the values.yaml file retains all original data and keys, with no functional changes besides setting some default CPU limits to null for service mesh components.
• Ran a local Helm install to ensure the chart still loads successfully and that the comments render as expected in the generated ConfigMap.

How I expect reviewers to test this PR

1. Check the values.yaml diffs: Confirm that all existing settings are untouched aside from the new doc blocks and null CPU limit changes for mesh components.
2. Validate resource updates: (Optional) Perform a helm template or local deployment to see the changes in resource definitions, ensuring the new CPU limit settings appear as commented.
3. Review doc clarity: Make sure the new references to recommended production sizing are clear, and that instructions about using null CPU limits for mesh components are understandable.

Checklist

• Tests added (N/A or minimal since this is a doc-focused PR, but confirm if any Helm chart lint tests are relevant)
  • Updated the following to cover resource updatescharts/consul/test/unit tests:
    • connect-inject-deployment.bats
    • ingress-gateways-deployment.bats
    • mesh-gateway-deployment.bats
    • server-statefulset.bats
    • terminating-gateways-deployment.bats
• CHANGELOG entry added

[sriramr98]

Hey @natemollica-nm . Thanks for the PR

I can see a couple of acceptance tests failing. Since you've added/modified some tests, they might be related to it. Can you look into it and get it to a passing state?

[natemollica-nm]

Hey @natemollica-nm . Thanks for the PR

I can see a couple of acceptance tests failing. Since you've added/modified some tests, they might be related to it. Can you look into it and get it to a passing state?

Yes! I'll dig into it more this week 😅

[natemollica-nm]

@sriramr98

I'm able to pass all the failing acceptance tests from my local branch for the api-gateway acceptance tests that keep failing:

• TestAPIGateway_Tenancy (failing for acceptance, acceptance-tproxy, and acceptance-cni)

I haven't touched any of the acceptance test framework for this PR. Only Helm chart unit tests for the values.yaml changes I made.

Is this test flaky at all in your experience? Is there anything I can do on my end to ensure this test passes?