Fix compose: move pids limits into deploy.resources.limits

Newer docker compose treats pids_limit and deploy.resources.limits.pids
as the same setting and rejects the project when both are present
("can't set distinct values on 'pids_limit' and
'deploy.resources.limits.pids'"). The limits are now only set as
deploy.resources.limits.pids (same values).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

compose.yaml

@@ -9,7 +9,7 @@ services:
         limits:
           cpus: "${WEBSITE_CPUS:-0.25}"
           memory: ${WEBSITE_MEMORY:-64M}
-    pids_limit: 64
+          pids: 64
     networks:
       - wizard_website
 
@@ -29,7 +29,7 @@ services:
         limits:
           cpus: "${SERVER_CPUS:-1.0}"
           memory: ${SERVER_MEMORY:-512M}
-    pids_limit: 256
+          pids: 256
     networks:
       - wizard_api
       - wizard_internal
@@ -58,7 +58,7 @@ services:
         limits:
           cpus: "${AI_CPUS:-1.0}"
           memory: ${AI_MEMORY:-1G}
-    pids_limit: 256
+          pids: 256
     volumes:
       # Trained checkpoints; replace without rebuilding the image.
       - ./wizard_ai/models:/srv/models:ro