Make Arrow imports of known extension types strict - #11223

The Vector importer used to decline a field that was not a FixedSizeList of
floats with non-nullable elements, so the column imported as plain storage.
It now fails on a field that cannot store vectors, and accepts nullable
elements, such as the ones pyarrow writes. The array import drops the nulls
under null vectors and fails on a null element of a valid vector.

Signed-off-by: Connor Tsui <[email protected]>

The arrow.uuid and arrow.json importers declined a field that broke the
canonical spec of its type, so the column imported as plain storage. They
now fail on such a field and build their arrays with try_new instead of
panicking on a storage mismatch.

The arrow.uuid importer uses the check that arrow-rs implements, which
matches the spec. The arrow.json check of arrow-rs is stricter than the
spec, which reserves the fields of the metadata object for later additions,
and Arrow C++ reads a missing metadata key as empty metadata. So the
arrow.json importer accepts a missing key, an empty string, and any JSON
object, and it still checks the storage type. The arrow.json exporter now
checks its target field by the same rule, so a JSON column exports back to
the field that it imports from.

Signed-off-by: Connor Tsui <[email protected]>

When GeoArrow rejected a field, for example a list view layout or metadata
that is not JSON, the spatial importers fell back to the extension name
alone. The fallback guessed the dimension from the field names and dropped
the CRS, and the array import then declined the same field, so the column
became plain storage under an extension dtype. A field that names a GeoArrow
type now has to parse as that type, and the WKB importer fails instead of
declining.

Signed-off-by: Connor Tsui <[email protected]>

The spatial importers declined the LargeList layout, which GeoArrow
accepts, and kept the nullability that Arrow gives coordinates, so a column
with nullable-marked coordinates failed to match its own extension dtype.
They now import through ArrowSession::from_arrow_storage. Nullable-marked
levels import as the non-nullable levels that GeoArrow declares, nulls under
null geometries are dropped, and a null coordinate of a valid geometry fails
with an error that names the type.

Signed-off-by: Connor Tsui <[email protected]>

A literal whose field no importer accepts already stays in DataFusion. Now
that importers fail instead of declining, an importer can accept a field
and still reject its value, for example a vector literal with a null
element. That failure used to fail the whole conversion. It now leaves the
literal to DataFusion as well.

Signed-off-by: Connor Tsui <[email protected]>