[BUGFIX] Use the doctrine type instead of binding type in DataSet

This change uses the doctrine type instead of the type
bindingtype in `DataSet->import()` still ensuring that
the value is encoded with current implementation within
the TYPO3 Connection, while preparing to remove custom
handling and using Doctrine DBAL behavour. With this
modification both code paths are working.

Additionally, the columnname is now used for the created
types array effectly fixing a bug that this information
has not been used and fallback to database schema was
used anyway.

Releases: main, 9, 8

Author: sbuerk

Classes/Core/Functional/Framework/DataHandling/DataSet.php

@@ -79,15 +79,14 @@ public static function import(string $path): void
                 // types correctly (like Connection::PARAM_LOB) allows doctrine to create valid SQL
                 $types = [];
                 foreach ($element as $columnName => $columnValue) {
-                    $columnType = $tableDetails->getColumn($columnName)->getType();
+                    $types[$columnName] = $columnType = $tableDetails->getColumn($columnName)->getType();
                     // JSON-Field data is converted (json-encode'd) within $connection->insert(), and since json field
                     // data can only be provided json encoded in the csv dataset files, we need to decode them here.
                     if ($element[$columnName] !== null
                         && $columnType instanceof JsonType
                     ) {
                         $element[$columnName] = $columnType->convertToPHPValue($columnValue, $platform);
                     }
-                    $types[] = $columnType->getBindingType();
                 }
                 // Insert the row
                 $connection->insert($tableName, $element, $types);