feat: add GHCR build workflow and custom schema support

[JOY (JOY)]

Summary

• GitHub Actions Build Workflow: Thêm .github/workflows/deploy-docker.yml để tự động build và push ghcr.io/dos/crove-cal:latest lên GitHub Container Registry.
• Custom Schema Routing: Cấu hình PrismaPg adapter tự động lấy schema=cal từ DATABASE_URL để query đúng schema cal trên Supabase Postgres.
• Prisma Migrations Fix: Loại bỏ prefix public. khỏi các file migration để chạy trơn tru trên custom schema.

---

Note

Medium Risk
Rewrites already-applied Prisma migration SQL and changes how every Prisma client selects a schema, which can break migrate/deploy on existing databases. GHCR publish is lower risk but still production-facing.

Overview
Enables deploying this Cal.com fork against a non-public Postgres schema (e.g. Supabase schema=cal) and publishing images to GHCR.

Prisma clients now parse schema from the DB URL and pass it into PrismaPg (webapp packages/prisma plus API v2 read/write services). Historical migrations drop hardcoded public. prefixes so objects are created in the search-path schema. Container startup skips wait-for-it when DATABASE_HOST is unset.

A new workflow builds and pushes :latest and :sha images to ghcr.io on dev/main (and manual dispatch), with placeholder Next public URLs baked in at build time.

^{Reviewed by Cursor Bugbot for commit 583c417. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Welcome to Cal.diy, JOY (@JOY)! Thanks for opening this pull request.

A few things to keep in mind:

• This is Cal.diy, not Cal.com. Cal.diy is a community-driven, fully open-source fork of Cal.com licensed under MIT. Your changes here will be part of Cal.diy — they will not be deployed to the Cal.com production app.
• Please review our Contributing Guidelines if you haven't already.
• Make sure your PR title follows the Conventional Commits format.

A maintainer will review your PR soon. Thanks for contributing!

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_d1b110c0-b7a2-4dc9-b604-2b4a29871ce7)