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.

teamspeak-server/values.yaml

@@ -1,3 +1,13 @@
+resources:
+  # Limits are optional: memory and ephemeral-storage limits default to
+  # limitFactor x the request, an explicitly set limit always wins, and a
+  # CPU limit is only set when configured explicitly under "limits".
+  limitFactor: 3
+  requests:
+    cpu: 0.2
+    memory: 100Mi
+    ephemeral-storage: 100Mi
+
 storage:
   size: 25Gi
   storageClass: longhorn