Make autoCommit, maxRows, outFormat, etc. connection attributes rather than global properties

This is enhancement request to make the various SQL execution properties such as autoCommit, maxRows, or outFormat attributes of a connection whether directly established or acquired from a pool, and not global constants on the oracledb object itself.

I maintain an internal library for our developers that wraps around node-oracledb to provide a variety of conveniences like multiple named Oracle connections from external config, promisification, etc. I have had to do a measurable amount of extra engineering to work around the fact that something like autoCommit is a global property rather than a connection specific one.

Off the top of my head, I think this per connection configurability could be something many developers might like to use and not just myself. If I recall right, the Java JDBC driver works in this way where these behaviors are per connection and not at the global driver level.

No files or tests are named. Start by tracing how connection and pool APIs currently expose autoCommit, maxRows, and outFormat, then compare direct and pooled connections. Done means these execution properties can be configured per connection rather than only as global oracledb properties, with behavior covered for both acquisition paths.