tandoor: start_period 30s -> 240s (probes exhausted before gunicorn bound)

After the memory fix tandoor still never went healthy. The probe output was
'wget: can't connect to remote host (127.0.0.1): Connection refused' while the
app log was still printing 'Booting worker' / 'Running django-vite' -- i.e. the
app had simply not finished starting. With start_period 30s and retries 3 the
healthcheck gave up at roughly two minutes.

Campaign 7 catalog sweep.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Nn3VgQk9iwEGgyx6QJ2NvE

templates/tandoor/docker-compose.yml

@@ -40,7 +40,9 @@ services:
       interval: 30s
       timeout: 5s
       retries: 3
-      start_period: 30s
+      # A tandoor (django-vite + migrációk) lassan bindol: 30s alatt még
+      # "Connection refused" jött, és a próbák elfogytak, mielőtt elindult.
+      start_period: 240s
     labels:
       - "traefik.enable=true"
       - "traefik.http.routers.tandoor.rule=Host(`${SUBDOMAIN}.${DOMAIN}`)"