feat(compose): opt-in skipDefaultNetwork to avoid Traefik multi-network routing issues

[myagizmaktav]

Fixes #4807

Problem

addDokployNetworkToService unconditionally attaches every domain-linked compose service to both dokploy-network and the project's implicit default network (the fix for #3562). For services that don't need default-network connectivity (single-service compose apps, or apps managing their own explicit network topology), this dual attachment can make Traefik's Docker provider pick the wrong network's IP for routing — producing a persistent 502 that neither a same-container restart nor a Traefik config reload fixes, only a full container recreate does. Full repro/evidence in #4807.

Change

Adds an opt-in, backward-compatible per-domain boolean skipDefaultNetwork (default false) that lets a domain skip the default network attachment while keeping dokploy-network. Mirrors the existing stripPath-style per-domain flag pattern (same schema/validation/pick-list shape).

• packages/server/src/db/schema/domain.ts — new skipDefaultNetwork column (NOT NULL, default false) + added to apiCreateDomain/apiUpdateDomain pick lists
• packages/server/src/db/validations/domain.ts — added to the domainCompose zod schema (compose-only, since this only matters for compose deployments)
• packages/server/src/utils/docker/domain.ts — addDokployNetworkToService takes an optional skipDefaultNetwork param (defaults to false, i.e. unchanged behavior); call site passes domain.skipDefaultNetwork ?? false
• apps/dokploy/drizzle/0175_skip_default_network.sql + journal entry — migration for the new column
• New tests in network-service.test.ts covering the opt-in path (5 new cases); all existing cases for the default/unchanged path still pass as-is
• Updated 4 existing test fixtures (Domain mock objects in host-rule-format.test.ts, labels.test.ts, forward-auth.test.ts, traefik.test.ts) that needed the new required field for typecheck

Testing

pnpm --filter=@dokploy/server run typecheck   # clean
pnpm --filter=dokploy run typecheck           # clean (pre-existing, unrelated handle-tag.tsx Zod-version error only, confirmed present on canary before this change too)
npx vitest run --config __test__/vitest.config.ts __test__/compose/
# Test Files  26 passed (26)
#      Tests  146 passed (146)

Note on the migration snapshot

I don't have a local Postgres/drizzle-kit toolchain to regenerate apps/dokploy/drizzle/meta/*_snapshot.json. The schema.ts change and migration SQL are minimal and correct (single boolean column, matching the style of the existing 0174 migration) — happy to update the snapshot if you can point me at how you'd like it generated, or if this is something CI/your usual flow regenerates.

Open to discussion

This is meant as a starting point, not a final word on the design — happy to adjust naming (skipDefaultNetwork vs something else), whether this belongs on Domain vs Compose, or add a UI toggle if you'd like one wired in as a follow-up. Wanted to keep this PR focused on the minimal backend capability + tests first.