Fix Directus health check 403 errors (DEV-376)

Changed liveness probe from HTTP /server/health to TCP socket check
and readiness probe to use root path instead. The /server/health
endpoint in Directus v12+ requires authentication by default,
causing 403 responses that triggered pod restarts.

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

apps/directus/directus-deployment.yaml

@@ -133,15 +133,14 @@ spec:
             cpu: "1"
             memory: 2Gi
         livenessProbe:
-          httpGet:
-            path: /server/health
+          tcpSocket:
             port: 8055
           initialDelaySeconds: 60
           periodSeconds: 10
           timeoutSeconds: 5
         readinessProbe:
           httpGet:
-            path: /server/health
+            path: /
             port: 8055
           initialDelaySeconds: 30
           periodSeconds: 5