chore(helm): right-size resource requests/limits per cluster telemetry

Drop requests to match observed peak usage and widen CPU limits for
burst headroom (Burstable QoS). Backend, web, Postgres, and Dragonfly
all had requests == limits pinned at defaults well above measured
7-day peaks.

- backend: req 100m/128Mi -> 50m/64Mi, lim 100m/128Mi -> 200m/128Mi
- web:     req 100m/128Mi -> 50m/96Mi, lim 100m/128Mi -> 200m/128Mi
- postgres (CNPG): req 50m/256Mi -> 15m/128Mi, lim 200m/512Mi -> 100m/256Mi
- dragonfly: req 100m/128Mi -> 100m/72Mi, lim 100m/128Mi -> 150m/128Mi

RAM limits unchanged where reasonable to preserve OOM protection;
Dragonfly CPU request kept at 100m (peak 74m) but limit raised to
avoid throttling under brief bursts.

backend/deploy/helm/values.yaml

@@ -26,10 +26,10 @@ httpRoute:
 
 resources:
   requests:
-    cpu: 100m
-    memory: 128Mi
+    cpu: 50m
+    memory: 64Mi
   limits:
-    cpu: 100m
+    cpu: 200m
     memory: 128Mi
 
 autoscaling:
@@ -111,11 +111,11 @@ postgres:
   storageSize: 5Gi
   resources:
     requests:
-      cpu: 50m
-      memory: 256Mi
+      cpu: 15m
+      memory: 128Mi
     limits:
-      cpu: 200m
-      memory: 512Mi
+      cpu: 100m
+      memory: 256Mi
 
 # DragonflyDB (Redis-compatible) — managed by the DragonflyDB operator
 dragonfly:
@@ -125,9 +125,9 @@ dragonfly:
   resources:
     requests:
       cpu: 100m
-      memory: 128Mi
+      memory: 72Mi
     limits:
-      cpu: 100m
+      cpu: 150m
       memory: 128Mi
 
 # Migration job (Helm pre-install/pre-upgrade hook)

web/deploy/helm/values.yaml

@@ -26,10 +26,10 @@ httpRoute:
 
 resources:
   requests:
-    cpu: 100m
-    memory: 128Mi
+    cpu: 50m
+    memory: 96Mi
   limits:
-    cpu: 100m
+    cpu: 200m
     memory: 128Mi
 
 autoscaling: