chore: dry run migration push in ci

Terraform Format and Style 🖌`success`

Terraform Initialization ⚙️`success`

Terraform Validation 🤖`success`

Validation Output

``` Success! The configuration is valid. ```

Terraform Plan 📖`success`

Show Plan

``` terraform data.supabase_branch.all: Reading... data.supabase_branch.all: Read complete after 0s Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions: # supabase_settings.production will be created + resource "supabase_settings" "production" { + api = jsonencode( { + db_extra_search_path = "public,extensions" + db_schema = "public,storage,graphql_public" + max_rows = 1000 } ) + id = (known after apply) + project_ref = "cimpzzikygouamvsjwxa" } Plan: 1 to add, 0 to change, 0 to destroy. ───────────────────────────────────────────────────────────────────────────── Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now. ```

Pusher: @sweatybridge, Action: pull_request, Working Directory: supabase/remotes, Workflow: CI

supabase / supabase-action-example