remove redundant migrate-run-ops.mjs script

The run-ops database is migrated first-class by the @internal/run-ops-database
package's own prisma migrate deploy (its schema.prisma datasource reads
RUN_OPS_DATABASE_URL and it owns its own migrations dir), which the root
db:migrate already sweeps via turbo. The bespoke script instead ran prisma
migrate deploy from the control-plane database package against the run-ops DB,
applying the full control-plane migration history rather than the run-ops subset
— redundant with the native flow and wrong. Drop the script and its two script
entries (root package.json, database package.json).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: d-cs

internal-packages/database/package.json

@@ -18,7 +18,6 @@
     "generate": "prisma generate",
     "db:migrate:dev:create": "prisma migrate dev --create-only",
     "db:migrate:deploy": "prisma migrate deploy",
-    "db:migrate:run-ops": "node scripts/migrate-run-ops.mjs",
     "db:push": "prisma db push",
     "db:studio": "prisma studio",
     "db:reset": "prisma migrate reset",

package.json

@@ -12,7 +12,6 @@
     "build:force": "turbo run build --force",
     "build:db:seed": "turbo run build:db:seed",
     "db:migrate": "turbo run db:migrate:deploy generate",
-    "db:migrate:run-ops": "pnpm --filter @trigger.dev/database run db:migrate:run-ops",
     "db:seed": "turbo run db:seed",
     "db:studio": "turbo run db:studio",
     "db:populate": "turbo run db:populate",