feat(DEVWF-935): add deno script for running pg-delta

[sweatybridge]

What kind of change does this PR introduce?

feature

What is the new behavior?

$ supabase db diff --use-pg-delta

Additional context

Add any other context or screenshots.

[coveralls]

Pull Request Test Coverage Report for Build 20749972864

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 31 of 55 (56.36%) changed or added relevant lines in 3 files are covered.
• 10 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.1%) to 55.989%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
cmd/db.go	0	4	0.0%
internal/db/diff/pgdelta.go	28	48	58.33%

Files with Coverage Reduction	New Missed Lines	%
internal/gen/keys/keys.go	5	12.9%
internal/start/start.go	5	65.45%

Totals
Change from base Build 20457218033:	-0.1%
Covered Lines:	6843
Relevant Lines:	12222

---

💛 - Coveralls

[avallete]

LGTM

[sweatybridge]

@avallete btw do you know if pgdelta starts anything in the background that doesn't get killed on error? The deno worker exits successfully with migra.ts but not pgdelta.ts

[avallete]

Had a look up to it but nothing stands out.
Maybe in case of error the db connection needs to be manually closed ? 🤔

Also locally updated the implementation to:

try {
  const result = await createPlan(source, target, supabase);
  const statements = result?.plan.statements ?? [];
  for (const sql of statements) {
    console.log(`${sql};`);
  }
  throw new Error("aijdoaijdiosj");
} catch (e) {
  console.error(e);
  // // Force close event loop
  // throw new Error("");
}

And in such case, I get a proper exit:

➜  cli git:(develop) ✗ go run . db diff --use-pg-delta
Creating shadow database...
Initialising schema...
Seeding globals from roles.sql...
Diffing schemas...
<stack-trace>
error diffing schema: error running container: exit 1:              
Error: aijdoaijdiosj                                                
    at file:///var/tmp/sb-compile-edge-runtime/index.ts:18:9        
    at Object.runMicrotasks (ext:core/01_core.js:683:26)            
    at processTicksAndRejections (ext:deno_node/_next_tick.ts:59:10)
    at runNextTicks (ext:deno_node/_next_tick.ts:76:3)              
    at eventLoopTick (ext:core/01_core.js:182:21)                   
main worker has been destroyed                                      
                                                                    
Try rerunning the command with --debug to troubleshoot the error.
exit status 1

[sweatybridge]

It only hangs on error if I don't bubble it up, for eg. trying to diff a linked project (permission error due to temp role).