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.

satisfactory/values.yaml

@@ -11,11 +11,13 @@ server:
   messagingPort: 30888
   storage: 20Gi
   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".
+    # The game server holds a large world in memory, so the default factor
+    # stays at 2 to keep the limit at the previously published 8Gi.
+    limitFactor: 2
     requests:
       memory: "4Gi"
       cpu: "1"
-      ephemeral-storage: "5Gi"
-    limits:
-      memory: "8Gi"
-      cpu: "2"
-      ephemeral-storage: "10Gi"
+      ephemeral-storage: "5Gi"