fix: deploy DB migrations

[eduardoboucas]

We are generating migration files but we're not including them in the deployed files. This PR addresses that.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b161e8a7-531f-4e27-9f55-844234a969d3

📥 Commits

Reviewing files that changed from the base of the PR and between 3c5c76f and 4ab3c46.

📒 Files selected for processing (3)

• src/utils/deploy/deploy-site.ts
• src/utils/deploy/process-files.ts
• tests/integration/commands/deploy/deploy.test.ts

---

📝 Walkthrough

Summary by CodeRabbit

Release Notes

• New Features

  • Database migrations are now automatically included in site deployments and tracked in deployment checksums.

• Tests

  • Added integration tests validating deployment behavior with and without database migrations.

Walkthrough

This change introduces support for database migrations in the deployment process. The deploySite function now includes an optional DB migrations directory in the file hash calculation. A new helper function getDbMigrationsDistPathIfExists checks for the existence of the migrations directory and returns its path if present. The deployFileNormalizer is extended with logic to rewrite normalized paths for migration files to use a designated public URL path. Integration tests verify that migrations are correctly included in deployment requests when present and excluded when absent.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix: deploy DB migrations' clearly and concisely describes the main change: addressing the deployment of database migration files.
Description check	✅ Passed	The description directly relates to the changeset by explaining the problem (migration files not included) and solution (this PR addresses that).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/deploy-db-migrations

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

📊 Benchmark results

Comparing with 3c5c76f

• Dependency count: 1,059 (no change)
• Package size: 354 MB ⬆️ 0.00% increase vs. 3c5c76f
• Number of ts-expect-error directives: 356 (no change)