GEOMESA-3584 Derive geometry type + name information from geomesa SFT spec metadata

[cwdobbins]

GEOMESA-3584: Derive geometry tyes from their stored SFT metadata attibutes

Deferred from #3573.

Background

TrinoTypeMapper bound every geometry column to Point or generic Geometry — Pointwhen the column carried a __X_z2__ companion, Geometry otherwise. Consumers of the discovered GeoTools schema got no more than that, even though the table's geometry is often a precise subtype (LineString, Polygon, MultiPolygon, …).

Change

When an Iceberg table carries a GeoMesa-encoded SimpleFeatureType, schema discovery now parses it and binds each geometry attribute to the subtype it declares; it falls back to the previous naming heuristic when no SFT metadata is present.

• TrinoSchemaDiscovery reads the geomesa.sft.spec (and geomesa.sft.name) table properties from the Iceberg "<table>$properties" metadata table. The spec is parsed with GeoMesa's SimpleFeatureTypes.createType, and each geometry attribute's JTS binding drives the descriptor.
• TrinoTypeMapper.toDescriptor takes the resolved geometry binding Class.
• failsafe: an absent property, an unreadable $properties, or an unparseable spec all fall back to the Point | Geometry heuristic.
• Declared geomesa-utils explicitly in the datastore pom since SimpleFeatureTypes is now used directly.