feat: database backup/restore automation and read replica routing (#8…

[Benalex8797]

closes #880
closes #881
closes #882
closes #883

#880 — Database backup and restore automation

• Add BackupAutomationService with full/incremental pg_dump, SHA-256 checksum verification, S3 upload (AWS SDK + local-copy fallback), dry-run restore, PITR lookup, and retention cleanup
• Add three scheduled tasks: daily full backup (02:00 UTC), 6-hour incremental backup, weekly retention cleanup
• Extend backup router with new endpoints: POST /backup/trigger, GET /backup/restore-points, GET /backup/restore-points/:id, POST /backup/restore/:id, POST /backup/restore/:id/dry-run, GET /backup/pitr, GET /backup/pitr/at, GET /backup/records
• Update .env.example with all BACKUP_* and S3_* env vars
• Add BackupAutomationService unit tests (dryRunMode, full/incremental, restore, dry-run restore, PITR, retention, job handlers)

#881 — Read replica routing

• Extend ReadReplicaRouter with background health checks, lag-aware failover cooldown, session stickiness, disableReplica/enableReplica
• Add PrismaReplicaClient: transparent Proxy routes Prisma read ops (findUnique, findFirst, findMany, count, aggregate, groupBy) to healthy replicas with automatic primary fallback on error
• Add monitoring endpoints: GET /database/replicas, POST /database/replicas/:url/disable, POST /database/replicas/:url/enable
• Mount databaseRouter in index.ts; start/stop health checks on server lifecycle
• Add 51 tests (all passing), pre-existing 4-test suite unaffected

What this PR does

• Summary of the implemented changes related to issue(s) DevTooling: Implement Monorepo with Turborepo for Shared Packages #240 and DevTooling: Implement Real-Time Error Monitoring with Sentry and Custom Dashboards #242
• Any breaking changes introduced (if any)
• Any migrations or data changes (if applicable)

Changes

• List of notable files and modules touched (monorepo wiring, Sentry integration, dashboards, etc.)
• Notes about the Turborepo configuration, shared packages, and ESLint/TS config

Why

• Rationale for the changes and how they solve the Acceptance Criteria

How to test

• Steps to reproduce locally, including commands to run build/test
• Any environment variables needed (e.g., SENTRY_DSN)
• How to verify the dashboards/alerts configuration (stubs or real)

[vercel]

@Benalex8797 is attempting to deploy a commit to the smartdevs17's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@Benalex8797 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits