Fix logging for streaming and updateMany

[jatcwang]

Introduces three new functions in the high level API for Connection (doobie.hi.HC).

Fixes #533, #1888

These helpers offer a few improvements:

• Logging support
• Handle and log exceptions throw during the PreparedStatement creation (Some JDBC drivers do this if the table doesn't exist)
• A slighly simpler "flat" API for anyone that wants to customize their query

executeWithResultSet

This is a generalization for any query that executes a PreparedStatement and processes a ResultSet. This covers two cases:

• A normal select query (JDBC's executeQuery)
• An update which generates returned rows (i.e. RETURNING / .executeUpdate + .getGeneratedKeys)

All query methods like Query#to and Update#withUniqueGeneratedKeys have switched to use this internally.

executeWithoutResultSet

Similar to executeWithResultSet but for queries that doesn't need to process a ResultSet (i.e. simple updates).

Methods like Update's updateMany, update have switched to use this internally

stream

This will be replacing the existing stream method (which is currently deprecated because it doesn't support logging)

Query#stream and all the Update#withGeneratedKeys* have switched to this internally.

Further improvements can probably be made on top of these methods so users don't need to construct LoggingInfo themselves.