Add support for PgBouncer transaction pooling mode by allowing to disable prepared statements

[incpo]

What is the problem this feature would solve?

When trying to use Bun's SQL client with PgBouncer in transaction pooling mode, the connection fails because PgBouncer doesn't support prepared statements. Currently, there's no way to disable prepared statements in Bun's SQL client.

What is the feature you are proposing to solve the problem?

Add configuration options to the Database constructor to disable prepared statements:

What alternatives have you considered?

1. Using PgBouncer in session pooling mode instead of transaction pooling mode

   • Less performant
   • Doesn't scale
   • Defeats the purpose of using PgBouncer for connection pooling

2. Connecting directly to PostgreSQL (port 5432)

   • Removes the benefits of connection pooling
   • Not suitable for high-scale applications
   • Increases database connection load

3. Using different database clients

   • Loses Bun's performance benefits
   • Requires changing existing codebase
   • Adds unnecessary dependencies

[nicksrandall]

This could be solved by #17029