wger: probe and route port 8000 (the image exposes 8000, not 80)

With 2.6 pulling and booting, wger still sat unhealthy: the healthcheck got
wget rc=4 (network failure, not an HTTP error) because nothing listens on :80.
wger's own log says it plainly -- 'Using django's development server on port
8000...' -- and the image declares ExposedPorts {"8000/tcp"}.

Corrected both the healthcheck target and the Traefik loadbalancer port, which
was pointing at :80 as well (so routing would have failed even once healthy).

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/wger/docker-compose.yml

@@ -39,7 +39,7 @@ services:
         limits:
           memory: 384M
     healthcheck:
-      test: ["CMD", "wget", "--spider", "-q", "http://127.0.0.1:80"]
+      test: ["CMD", "wget", "--spider", "-q", "http://127.0.0.1:8000"]
       interval: 30s
       timeout: 5s
       retries: 3
@@ -50,7 +50,7 @@ services:
       - "traefik.http.routers.wger.entrypoints=websecure"
       - "traefik.http.routers.wger.tls=true"
       - "traefik.http.routers.wger.tls.certresolver=letsencrypt"
-      - "traefik.http.services.wger.loadbalancer.server.port=80"
+      - "traefik.http.services.wger.loadbalancer.server.port=8000"
 
 volumes:
   wger_data: