fix(orchestrator): copy schema file after COPY to overwrite dangling symlink

Kaniko does NOT follow symlinks — it copies them as-is. The symlink
apps/orchestrator/prisma/schema.prisma → ../../api/prisma/schema.prisma
becomes dangling inside the container since apps/api/ is not present.

Fix: explicitly copy apps/api/prisma/schema.prisma to
apps/orchestrator/prisma/schema.prisma AFTER the COPY apps/orchestrator
step. This overwrites the symlink with the actual file content.

CI still works via the symlink (full monorepo checkout resolves it).
Docker now has the real file at the expected path.

apps/orchestrator/Dockerfile

@@ -47,11 +47,10 @@ COPY --from=deps /app/packages/shared/node_modules ./packages/shared/node_module
 COPY --from=deps /app/packages/config/node_modules ./packages/config/node_modules
 COPY --from=deps /app/apps/orchestrator/node_modules ./apps/orchestrator/node_modules
 
-# The repo has apps/orchestrator/prisma/schema.prisma as a symlink for CI use.
-# Kaniko resolves destination symlinks on COPY, which fails because the symlink
-# target (../../api/prisma/schema.prisma) doesn't exist in the container.
-# Fix: remove the dangling symlink first, then copy the real schema file there.
-RUN rm -f apps/orchestrator/prisma/schema.prisma
+# Overwrite the symlink (apps/orchestrator/prisma/schema.prisma → ../../api/prisma/schema.prisma)
+# with the real file content. Kaniko copies symlinks AS symlinks (does not follow them),
+# so the symlink target would be dangling inside the container. Copying the actual file
+# after the orchestrator COPY overwrites the symlink with the resolved content.
 COPY apps/api/prisma/schema.prisma ./apps/orchestrator/prisma/schema.prisma
 # pnpm turbo build runs prisma:generate (--schema=./prisma/schema.prisma) from the
 # orchestrator package context — no cross-package project-root issues.