fix: use custom migrate.ts instead of drizzle-kit migrate in Docker

drizzle-kit migrate exits 0 even when migrations fail, so the server
would start on a broken schema. The custom migrate.ts uses drizzle-orm's
programmatic migrator and calls process.exit(1) on failure, which
prevents the server from starting and makes failures visible in Coolify.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Dockerfile

@@ -30,9 +30,10 @@ COPY --from=install /usr/src/app/node_modules node_modules
 COPY --from=build /usr/src/app/package.json ./package.json
 COPY --from=build /usr/src/app/drizzle.config.ts ./drizzle.config.ts
 COPY --from=build /usr/src/app/drizzle ./drizzle
+COPY --from=build /usr/src/app/src/server/db/migrate.ts ./migrate.ts
 
-RUN chmod -R a+rX drizzle public
+RUN chmod -R a+rX drizzle public migrate.ts
 
 USER bun
 EXPOSE 3000
-CMD ["sh", "-c", "bun run db:migrate && bun server.js"]
+CMD ["sh", "-c", "bun migrate.ts && bun server.js"]