fix(orchestrator): copy schema into orchestrator/prisma/ for local prisma generate

Prisma was climbing the directory tree to find a project root and landing at
/app/apps/ which has no package.json. Fix: copy the API schema directly into
apps/orchestrator/prisma/schema.prisma and run generate from within the
orchestrator package context using node_modules/.bin/prisma directly.

This keeps prisma generate fully self-contained within the orchestrator package
and avoids all cross-package project-root detection issues.

apps/orchestrator/package.json

@@ -7,7 +7,7 @@
     "dev": "nest start --watch",
     "lint": "eslint src/",
     "lint:fix": "eslint src/ --fix",
-    "prisma:generate": "prisma generate --schema=../api/prisma/schema.prisma",
+    "prisma:generate": "prisma generate --schema=./prisma/schema.prisma",
     "start": "node dist/main.js",
     "start:debug": "nest start --debug --watch",
     "start:dev": "nest start --watch",
@@ -52,5 +52,8 @@
     "tsconfig-paths": "^4.2.0",
     "typescript": "^5.8.2",
     "vitest": "^4.0.18"
+  },
+  "prisma": {
+    "schema": "prisma/schema.prisma"
   }
 }