Since v3, Doctrine DBAL supports adding custom driver
middlewares. These middlewares act as a decorator around
the actual `Driver` component.
Since #100089 it's possible to configure driver middlewares
for a specific database connection based on the Doctrine DBAL
driver middlewares along with some specific middlewares.
To prepare for Doctrine DBAL v4 upgrade, a mandantory global
driver middleware `CustomPlatformDriverMiddleware` has been
added with #102402.
With this feature, global connection driver middlewares are
now added as a configurable option and the already specific
core middleware is added to the default configuration.
Global driver middlewares can now be configured in
/** array<int|string, string> **/
$GLOBALS['TYPO3_CONF_VARS']['DB']['globalDriverMiddlewares']
and are replaced with the specific connection driver middlewares.
The `global` => `specific` order allows to register a global
middleware, but disable it for a specific middleware later on.