http connection parameters

[jawj]

Changes which (amongst other benefits) support OIDC auth for Neon partners:

• Options to the neon(...) HTTP-client creation function, and to the transaction and query functions, now support individual connection parameters: user (or username), password, host (or hostname), port, database and connectionString.

  These can be strings (or number, for port) or sync or async functions to be resolved on every query. They can supplement, override parts of, or fully replace the first-argument connection string.

  So this still works:

  • const sql = neon(DATABASE_URL)

  But, for example, these now work too:

  • const sql = neon(DATABASE_URL_NO_PASSWORD, { password: () => getPasswordAsync() })
  • const sql = neon({ user, password, host, database })
  • const sql = neon({ connectionString: () => getConnectionString() }

• Client and Pool now support a sync or async function as the password connection parameter when pipelineConnect is enabled (this previously caused an error).

• parseIntoClientConfig is exported, to support supplementing a connection string with a function to retrieve a token as password (recent changes exported parseConnectionString instead, but this turns out to be more suitable).

Smaller changes:

• HTTP-related code has been refactored into its own folder, with NeonDbError and NeonQueryPromise getting their own files.

• application_name is now used to report the driver identity and version to the proxy, unless overridden.

• Minor fixes to TLS handling, addressing two PRs.

• A few minor dependency updates.

[pffigueiredo]

Should we also add docs about these:

• parseIntoClientConfig
• Function passwords for Client/Pool