Rework logger as a driver middleware

[morozov]

The current SQLLogger has major disadvantages:

1. It doesn't log exceptions (New Logger interface #3228) or anything else (Add query backtrace logger #3513) besides what's hard-coded in the wrapper connection.
2. It's not extensible. Any addition to the interface would be a breaking change.
3. It's not PSR-compliant.
4. It's not a logger (Add query backtrace logger #3513 (comment)).

As of DBAL 3.0 (#4157), the Middleware interface is available which could be used to implement logging. It could log connecting, disconnecting, executing queries and prepared statements, numbers of fetched and affected rows, errors, and all other details that are available at the driver level API. The end-users will be able to extend it by implementing their own logging functionality without the need to change the API.

[morozov]

PoC: 3.2.x...morozov:issues/4941-logging-middleware. Need to change the way we identify drivers in the test suite.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.