TYPO3 Core

Doctrine DBAL 4.x removed the feature to save specific type
information as part of the column comment and for reading
the database schema with `AbstractSchemaManager` hierarchy
classes.

That also includes the option to enable and disable this
feature along with setting in type classes which needs to
write the custom information in case used database do not
support it natively - or for implemented custom type.

Doctrine postulate that it is the responsibility of the
application or framework to keep track of a precise and
cross database schema on own behalf, where the provided
schema information retrieved with the Doctrine DBAL
`AbstractSchemaManager` implementation are types which
would produce the same database structure for that vendor.

The possible TYPO3 counterpart for expected field types is
`$GLOBALS['TCA']` (TcaSchemaFactory), but does not really
ensure to hold all information, because TYPO3 allows extension
authors to define tables not managed by TYPO3 (TCA) with
`ext_tables.sql` files.

With #99062 the introduction of the native JSON database field
support it has been postulated that simply providing an array
for `Connection` methods like `insert` or `update` and using
`DataHandler` for TCA-type JSON handles this for all databases,
even if not nativly supported. That broke in TYPO3 v13 due to
the breaking change of Doctrine.