fix: put Traefik labels back, scoped to coolcouch, pinned to UUID net

The previous diagnostic showed Coolify does not auto-inject Traefik
labels just because SERVICE_FQDN_<NAME>_<PORT> is set — the container
had zero traefik.* labels after deploy, which is why the host returned
503. Adding explicit router+service labels and binding the docker
provider to the per-resource UUID network gives Traefik a definite
backend. Router/service names use the coolcouch prefix so they cannot
clash with any Coolify-managed couchdb router on the same install.

docker-compose.yml

@@ -13,6 +13,13 @@ services:
     networks:
       - default
       - coolify
+    labels:
+      - "traefik.enable=true"
+      - "traefik.docker.network=${COOLIFY_RESOURCE_UUID}"
+      - "traefik.http.routers.coolcouch.rule=Host(`${SERVICE_FQDN_COUCHDB_5984}`)"
+      - "traefik.http.routers.coolcouch.entrypoints=https"
+      - "traefik.http.routers.coolcouch.tls=true"
+      - "traefik.http.services.coolcouch.loadbalancer.server.port=5984"
 
   couchdb-init:
     image: curlimages/curl:latest