Fix Dozzle connection issues and restarts

Root cause: Dozzle was being rate-limited by the Kubernetes API when
fetching logs from many containers. The aggressive 1-second health check
timeouts caused the container to fail probes and restart repeatedly.

Changes:
- Increased all probe timeouts from 1s to 5s to handle API rate limiting
- Increased liveness probe period from 10s to 30s to reduce check frequency
- Increased readiness probe period from 5s to 10s
- Increased startup probe failure threshold from 15 to 20 (60s total startup time)
- Increased CPU limit from 500m to 1000m and request from 100m to 250m
- Increased memory limit from 512Mi to 1Gi and request from 128Mi to 256Mi
- Pinned image version to v10.6.10 instead of :latest

This prevents unnecessary restarts when Dozzle is waiting on rate-limited
Kubernetes API calls, fixing both the initial 503 errors and the connection
drops after prolonged use.

Resolves: DEV-351

Co-Authored-By: Paperclip <noreply@paperclip.ing>

apps/dozzle/deployment.yaml

@@ -42,25 +42,25 @@ spec:
           httpGet:
             path: /healthcheck
             port: 8080
-          initialDelaySeconds: 5
-          periodSeconds: 2
-          timeoutSeconds: 1
+          initialDelaySeconds: 10
+          periodSeconds: 3
+          timeoutSeconds: 5
           successThreshold: 1
-          failureThreshold: 15
+          failureThreshold: 20
         readinessProbe:
           httpGet:
             path: /healthcheck
             port: 8080
-          periodSeconds: 5
-          timeoutSeconds: 1
+          periodSeconds: 10
+          timeoutSeconds: 5
           successThreshold: 1
-          failureThreshold: 2
+          failureThreshold: 3
         livenessProbe:
           httpGet:
             path: /healthcheck
             port: 8080
-          periodSeconds: 10
-          timeoutSeconds: 1
+          periodSeconds: 30
+          timeoutSeconds: 5
           successThreshold: 1
           failureThreshold: 3
         volumeMounts:
@@ -68,11 +68,11 @@ spec:
           mountPath: /data
         resources:
           limits:
-            cpu: 500m
-            memory: 512Mi
+            cpu: 1000m
+            memory: 1Gi
           requests:
-            cpu: 100m
-            memory: 128Mi
+            cpu: 250m
+            memory: 256Mi
       - name: oauth2-proxy
         image: quay.io/oauth2-proxy/oauth2-proxy:latest
         ports: