Feat/concurrent deployments in memory queue - #4645

Resolves conflicts with 16 upstream commits, notably:
- Renumber caddy migration 0172_parched_ares -> 0173_cool_vargas
  (upstream 0172_quick_the_professor from concurrent deployments Dokploy#4645
  is canonical); regenerated snapshot on top of upstream's, restored
  idempotent DDL so hosts that applied the old identity no-op cleanly
- Adopt dynamic traefik container resolution in access-log cleanup
  (Dokploy#4646) within the provider-aware handler
- Accept admin-tools refactor (Dokploy#4625): traefik file-system modal is
  deleted; /dashboard/traefik page with ServerFilter is now the entry
  point and is cloud-enabled, ShowTraefikSystem stays provider-aware
  with a provider-aware empty state path
- Fold buildsConcurrency (server + webServerSettings) alongside caddy
  provider columns in db schema
- Tailwind v4 class renames (shadow-xs, h-140) applied to our
  provider-aware components, keeping caddy language switch and
  pointer-events-none read-only overlay fix

Co-Authored-By: Claude Fable 5 <[email protected]>

Upstream's concurrent deployments (Dokploy#4645) allow builds to finish
simultaneously. The active caddy.json is compiled from the fragments
directory, so an unsynchronized read-compile-write could publish a
config missing a concurrently written fragment, and the rm-rf-based
restoreCaddyRouteFragments rollback could delete another deployment's
fragment outright. Add a per-server promise-chain lock; the public
compile+reload entry takes it, and the fragment read-modify-write flows
(application domains, compose domains, dashboard route) hold it across
their full capture-mutate-compile-rollback sequences.

Co-Authored-By: Claude Fable 5 <[email protected]>

…oncurrency impl, keep network management)

Sync fork to Dokploy v0.29.11 (tag 1c44141). Conflict policy:
- Upstream wins by default on all overlapping code.
- DROP the fork's concurrent-deployments implementation (superseded by
  upstream Dokploy#4645 + v0.29.11 OSS concurrent builds): took upstream's
  deployments-queue.ts, queueSetup.ts, server.ts, routers, schema, and
  UI; deleted queue-routing.ts / job-context.ts / concurrency modals /
  concurrency tests; reverted execAsync.ts and pages/api/deploy/*.ts.
- KEEP the fork's Docker network-management feature (no upstream
  equivalent), re-integrated onto upstream's Tailwind-v4-refactored
  files: network router registration, nav entry, per-service network
  cards, schema relations/exports, and per-resource attach hooks.
- Fork-owned files kept ours: README.md, CNAME, install.sh,
  .github/workflows/dokploy.yml, services/settings.ts fork sources.
- Version set to v0.29.11-devino.1.

Drizzle network migration regeneration + sync playbook + .gitattributes
merge=ours drivers follow in subsequent commits.

Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_013BDnry4m2EoRRM1LdvEmqV