Add unusable postgres client behind a canary-or-debug-only feature flag

[Jarred-Sumner]

What does this PR do?

Bring back #6531

This isn't ready yet, but I don't want it to bitrot - so what if we merge this behind a canary/debug-only feature flag?

The main issues are:

1. GC isn't being handled correctly when creating results, which leads to a crash after enough of the tests run. This makes it unusable for more than a brief period
2. TLS is not at all implemented yet
3. Only prepared statements are supported
4. No helper for transactions
5. Only SCRAM-SHA-256 password auth is implemented. MD5 digest, GSSPI, TLS, etc are not implemented yet.
6. Error messages from Postgres are almost unreadable
7. Various polish details are not implemented. sql.array, command property, number of changes, no way to transform values etc. I think we could get away with shipping a v1 that lacks most polish details though

How did you verify your code works?

[github-actions]

❌ @Jarred-Sumner, your commit has failing tests :(

🪟💻 3 failing tests Windows x64 baseline

• test/cli/install/bun-add.test.ts 1 failing
• test/cli/install/registry/bun-install-registry.test.ts 1 failing
• test/integration/expo-app/expo.test.ts 1 failing

🪟💻 3 failing tests Windows x64

• test/cli/install/bun-add.test.ts 1 failing
• test/cli/install/registry/bun-install-windowsshim.test.ts code 1
• test/integration/next-pages/test/dev-server.test.ts 1 failing

View logs