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.

zipline/templates/zipline.sfs.yaml

@@ -36,14 +36,7 @@ spec:
             - name: UPLOADER_ADMIN_LIMIT
               value: 500mb
           resources:
-            requests:
-              memory: "{{ .Values.zipline.resources.requests.memory }}"
-              cpu: "{{ .Values.zipline.resources.requests.cpu }}"
-              ephemeral-storage: "{{ .Values.zipline.resources.requests.ephemeralStorage }}"
-            limits:
-              memory: "{{ .Values.zipline.resources.limits.memory }}"
-              cpu: "{{ .Values.zipline.resources.limits.cpu }}"
-              ephemeral-storage: "{{ .Values.zipline.resources.limits.ephemeralStorage }}"
+            {{- include "zipline.resources" .Values.zipline.resources | nindent 12 }}
           ports:
             - name: "zipline-server"
               containerPort: 3000