Branching silently wedges when source Postgres patch version is older than the latest

## Bug Creating a development branch from a project running an older Postgres patch version succeeds at the API level (`201` returned with a branch record) but never finishes provisioning. The branch sits in `status: CREATING_PROJECT` / `preview_project_status: COMING_UP` indefinitely. The branch's DB hostname never resolves (NXDOMAIN). No error is surfaced anywhere — UI, API, or logs. The root cause appears to be that branches are provisioned on the **latest Postgres patch version**, but the source project is on an **older** patch. Cross-version branch creation hangs without erroring. ## Reproduction 1. Project on `17.6.1.084` (release channel `ga`), Pro plan, region `us-east-2`. The project upgrade-eligibility endpoint confirms the gap: `eligible:true`, `current_app_version: …084`, `latest_app_version: …105`. 2. Create a branch via the Management API: ```bash curl -X POST "https://api.supabase.com/v1/projects/{REF}/branches" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{"branch_name":"test","region":"us-east-2"}' ``` 3. Branch is returned with `status: CREATING_PROJECT` (HTTP 201). Poll the branch detail and the parent project's branches list. 4. After 20–30+ minutes the status is still `CREATING_PROJECT` / `preview_project_status: COMING_UP`. `branch.updated_at` never advances past the `created_at` timestamp. 5. The branch's DB hostname never resolves: ``` $ host db.{branch_ref}.supabase.co Host db.{branch_ref}.supabase.co not found: 3(NXDOMAIN) ``` 6. The branch project's health endpoint reports every service `UNHEALTHY`: ```bash curl "https://api.supabase.com/v1/projects/{branch_ref}/health?services=db,pooler,realtime,rest,auth,storage" \ -H "Authorization: Bearer $TOKEN" ``` Returns: ```json [ {"name":"db","status":"UNHEALTHY","error":"ipv6 address is not defined"}, {"name":"pooler","status":"UNHEALTHY","error":"{\"error\":\"not found\"}…