TYPO3 Core

Doctrine DBAL 4.2.0 implemented the `EnumType`, which TYPO3
provides already for a long time. The way it has been added
breakes the TYPO3 implementation.

The TYPO3 implementation does not supported other dbms then
MariaDB/MySQL. The new DBAL implementation does not contain
a fully working replacement retrieving the same type again.
At least database analyzer benefits from the Doctrine DBAL
type and can create compatible fields for database systems
not having native `ENUM` support when replaced. Thus, type
implementation is now switched using the dbal implementation.
Thus, adding replacement code at different places can be
avoided, keeping the current state and even improving it
slightly.

[1] https://github.com/doctrine/dbal/releases/tag/4.2.0