chore(db): finish Prisma cutover to Drizzle Kit tooling

Move CMS SQL to drizzle/migrations, drop prisma packages/schema, wire drizzle-kit scripts, and regenerate schema names from src/db/schema.ts.

Co-authored-by: Cursor <[email protected]>

.gitea/workflows/ci.yaml

@@ -43,7 +43,7 @@ jobs:
           export REDIS_URL="redis://127.0.0.1:6379?connect_timeout=1"
           export BCRYPT_ROUNDS=4
           pnpm install --frozen-lockfile
-          # Types come from the committed Drizzle schema (src/db/schema.ts); no prisma:generate.
+          # Types come from the committed Drizzle schema (src/db/schema.ts).
           pnpm biome:lint
           pnpm typecheck
           pnpm test
@@ -139,7 +139,7 @@ jobs:
           echo "STAGE DATABASE_POOL_SIZE=${DATABASE_POOL_SIZE}"
 
           pnpm install --frozen-lockfile
-          # Types come from the committed Drizzle schema (src/db/schema.ts); no prisma:generate.
+          # Types come from the committed Drizzle schema (src/db/schema.ts).
           export BCRYPT_ROUNDS=4
           pnpm typecheck
           # Validate production env (AUTH_SECRET, DATABASE_URL, …) during build.
@@ -292,7 +292,7 @@ jobs:
           export NODE_ENV=production
           export SKIP_ENV_VALIDATION=1
           pnpm install --frozen-lockfile
-          # Types come from the committed Drizzle schema (src/db/schema.ts); no prisma:generate.
+          # Types come from the committed Drizzle schema (src/db/schema.ts).
           # Tag releases must apply CMS SQL migrations against the live DB
           # (same path as push-to-main deploy), using the production .env.
           LIVE="/var/www/atom-nexst"