Make the Docker build and compose smoke test pass

Fixes found while validating `docker compose up`:
- Copy .editorconfig into the build context and stop ignoring it — the in-container
  publish needs its analyzer suppressions (CA1848/CA1873) or warnings-as-errors fails.
- npm ci uses npmjs.org (the Nexus npm proxy 404s on some packages; npmjs.org is
  reachable from this machine); base images + NuGet still go through the mirror.
- Parameterize the Postgres/web host ports (defaults 5432/8080) so the stack doesn't
  clash with other local Postgres instances.

Verified: image builds; `compose up` brings up Postgres (healthy) + web + worker on one
image (RUN_MODE) — /health 200, /api/orgboard/ping ok, the SPA serves at /, and the
worker logs "DB health: Healthy" heartbeats.

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

docker/docker-compose.yml

@@ -11,7 +11,8 @@ services:
       POSTGRES_USER: teamup
       POSTGRES_PASSWORD: teamup
     ports:
-      - "5432:5432"
+      # Host port is configurable to avoid clashes with other local Postgres instances.
+      - "${POSTGRES_HOST_PORT:-5432}:5432"
     volumes:
       - pgdata:/var/lib/postgresql/data
       - ./postgres-init.sh:/docker-entrypoint-initdb.d/01-init-vector.sh:ro
@@ -34,7 +35,7 @@ services:
       # The web role applies migrations; the worker waits (EF's DB-wide lock makes it safe either way).
       Database__ApplyMigrationsOnStartup: "true"
     ports:
-      - "8080:8080"
+      - "${WEB_HOST_PORT:-8080}:8080"
     depends_on:
       postgres:
         condition: service_healthy