#4007 fix(ci): unblock production deploys from read-replica schema sync

Summary (AI generated)

• Restored .github/workflows/build_and_deploy.yml to the pre–Oct 28 subscription layout (base commit 3a8537cbf), with no read_replica_schema / read_replica_subscription jobs and no CI invocation of scripts/sync-read-replica-schema.ts.
• Kept the later #3906 deploy-scope change: no deploy_r2_inventory job / r2_inventory output (inventory consumer is no longer part of this workflow).
• Updated release workflow unit tests to assert read-replica sync is absent from deploy CI.

Motivation (AI generated)

Read-replica schema/subscription sync in deploy CI caused production release breakage. Martin runs replica sync manually when needed; deploy must not gate on it.

Business Impact (AI generated)

Unblocks Capgo production releases without risking worker deploy stalls on Google Cloud SQL / publication refresh.

Test Plan (AI generated)

• bun test tests/read-replica-release-workflow.unit.test.ts tests/read-replica-schema-new-table.unit.test.ts tests/capgo-release-workflow.unit.test.ts
• Full CI on PR

Generated with AI

  

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

Summary by CodeRabbit

• Deployment Updates
  • Production releases no longer wait for read-replica schema reconciliation. Supabase deployments, application and service deployments, and schema-type synchronization now proceed according to their existing change-scope and deployment conditions. This updates the release sequence without changing the scope checks or production requirements for schema-type synchronization.