Harden pod and container security contexts across all workloads

Add securityContext hardening (runAsNonRoot, readOnlyRootFilesystem,
capabilities drop ALL, allowPrivilegeEscalation false) to the 10 workloads
that lacked it: apache-tika, cyberchef, gotenberg, homeassistant,
matrix-delegation-nginx, paperless-server, paperless-consume cronjob
(plus automountServiceAccountToken false), patchmon-frontend,
urlaubsverwaltung and zipline. All contexts are configurable via
securityContext.pod / securityContext.container in values.yaml; writable
paths are provided as emptyDirs. Image-forced deviations (Home Assistant
root start for s6-overlay + NET_RAW for discovery, paperless root init
container for /run ownership) are documented in the charts' values.yaml.
Major version bump for every changed published chart.

cyberchef/values.yaml

@@ -1,4 +1,23 @@
 cyberchef:
+  # The upstream image is stock nginx (root, listening on port 80). To still
+  # run fully non-root, the pod runs as the image's nginx user (uid 101) and
+  # the safe sysctl net.ipv4.ip_unprivileged_port_start=80 lets the unprivileged
+  # nginx bind port 80 without NET_BIND_SERVICE.
+  securityContext:
+    pod:
+      runAsNonRoot: true
+      runAsUser: 101
+      runAsGroup: 101
+      sysctls:
+        - name: net.ipv4.ip_unprivileged_port_start
+          value: "80"
+    container:
+      allowPrivilegeEscalation: false
+      readOnlyRootFilesystem: true
+      runAsNonRoot: true
+      capabilities:
+        drop:
+          - ALL
   livenessProbe:
     httpGet:
       path: /