Compute memory/ephemeral-storage limits from requests, drop default CPU limits

Every chart now renders its container resources through a duplicated
_helpers.tpl helper (reference implementation in template-chart): requests
ship as chart defaults, missing memory and ephemeral-storage limits are
computed as resources.limitFactor x the request (default 3, satisfactory
keeps 2 to preserve its previously published 8Gi limit), an explicitly set
limit always wins, and a CPU limit is only rendered when set explicitly.
Fixed limit defaults are removed from all values.yaml files; teamspeak-server
gains a values-driven resources block instead of hardcoded template values.
Major version bump for all published charts.

gotenberg/Chart.yaml

@@ -4,7 +4,7 @@ description: A Helm chart to deploy Gotenberg on Kubernetes
 
 type: application
 
-version: 3.0.0+up8.26.0
+version: 4.0.0+up8.26.0
 appVersion: "8.26.0"
 
 maintainers: