chore(deps): upgrade to latest pgpm/supabase-test and align toolchain with constructive

[pyramation]

Summary

Brings the suite up to the latest published toolchain, most importantly the test harness:

• supabase-test: ^0.4.16 → ^3.8.2 (the big jump — this is the harness the tests import getConnections/PgTestClient from; version synced from the constructive monorepo via makage update-deps).
• Remaining devDeps aligned to the exact versions constructive uses (the ecosystem source-of-truth), rather than bleeding-edge:
  • jest 29 → ^30.4.2, @types/jest 29 → ^30.0.0, ts-jest ^29.4.11 (jest30 + ts-jest29 is the known-good combo in constructive)
  • @types/node ^22.19.11, @typescript-eslint/* ^8.59.4, eslint ^9.39.2, eslint-config-prettier ^10.1.8, eslint-plugin-unused-imports ^4.4.1, prettier ^3.8.1, rimraf 4 → ^6.1.3, typescript ^5.9.3.

Deliberately avoided the pre-release/major jumps that pnpm up -L initially pulled (typescript@7.0.2, eslint@10, lerna@9, @types/node@26) because they break the eslint/ts-jest peer ranges and diverge from constructive.

Validation

• pnpm install clean.
• pnpm -r lint passes on the upgraded toolchain.
• npx tsc --noEmit passes — supabase-test@3.8.2's API (getConnections, PgTestClient) typechecks unchanged against the existing tests, so no source changes were needed.
• Not run here: the full jest suite, which requires a live Supabase local stack (supabase start, port 54322) as the CI workflow does; no source/test behavior changed, only dependency versions.

Link to Devin session: https://app.devin.ai/sessions/025fb88043964fdbb335ac5e39df2478
Requested by: @pyramation

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	jest@​30.4.2
	@​typescript-eslint/​parser@​8.65.0
	@​types/​jest@​30.0.0
	lerna@​8.2.4
	@​typescript-eslint/​eslint-plugin@​8.65.0
	@​types/​node@​22.20.1
	rimraf@​6.1.3
	eslint-config-prettier@​10.1.8
	eslint-plugin-unused-imports@​4.4.1
	ts-jest@​29.4.12
	eslint@​9.39.5
	prettier@​3.9.6

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @launchql/protobufjs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@launchql/protobufjs@7.2.6 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@launchql/protobufjs@7.2.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @protobufjs/float is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@protobufjs/float@1.0.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@protobufjs/float@1.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm lerna is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → npm/lerna@8.2.4 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lerna@8.2.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/jest@30.4.2 → npm/lerna@8.2.4 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report