Replace ESRI geometry library with JTS in geospatial plugin

[dain]

Description

Migrate the geospatial plugin from ESRI geometry-api-java to JTS (Java Topology Suite) as the core geometry library. JTS is more widely used, better maintained, and provides the foundation for upcoming Iceberg geometry type support.

Key changes:

• Use JTS Geometry as the native stack type instead of serialized bytes
• Replace custom geometry serialization with standard EWKB format
• Convert all geometry functions (ST_*, Bing tiles, aggregations, spatial joins)
• Simplify Hadoop ESRI JSON reader and PostgreSQL connector geometry handling

Additional context and related issues

JTS is the de facto standard geometry library in the Java ecosystem, used by GeoTools, PostGIS, and Apache Sedona. This change aligns Trino's geospatial implementation with the broader ecosystem and enables future improvements like Iceberg geometry support.

Reviewer Guide

Commit Organization

The migration is structured to minimize risk and make review manageable:

1. Test infrastructure first: Initial commits separate Repairs (fixing invalid OGC inputs
   like unclosed rings that JTS correctly rejects) from Refactors (adding assertSpatialEquals to
   handle harmless differences like vertex ordering). Any test changes in subsequent commits indicate
   actual behavior differences between ESRI and JTS.
2. Incremental function conversion: Functions are ported in logical groups:
   • Basic geometry functions (ST_Boundary, ST_Buffer, etc.)
   • Accessor functions (ST_NumPoints, etc.)
   • EncodedPolyline, BingTile, aggregation functions
   • ST_Union and remaining GeoFunctions
   • Spatial join and envelope handling
3. Serialization change: Replaces custom binary format with EWKB (Extended Well-Known Binary),
   the PostGIS standard that preserves SRID.
4. Hadoop reader: Converted separately due to Maven dependency constraints.
5. Import cleanup: Using qualified imports for JTS objects removes the fully-qualified names that
   were needed while both libraries coexisted. Please do not comment on verbose imports in earlier commits.
6. Stack type change: Final commit switches from Slice to JTS Geometry as the native stack type,
   eliminating serialization cycles between function calls.

Behavior Differences

Test changes document intentional behavior differences:

• ST_Buffer approximation: JTS uses 8 segments per quadrant (matching PostGIS/GEOS standards) by
  default, whereas ESRI used 24. This results in buffer polygons with fewer vertices (e.g., 32 vs 96 for
  a point buffer) while maintaining standard precision.
• ST_NumPoints: Now counts the closing vertex of polygons, complying with the OGC standard (where a
  triangle has 4 points: A-B-C-A).
• ST_Boundary: Returns LINESTRING instead of MULTILINESTRING for simple polygons (simpler, more
  standard return type).
• Empty Geometries: ST_Buffer(infinity) returns POLYGON EMPTY (instead of MULTIPOLYGON EMPTY).
• ST_Union: Returns an empty GEOMETRYCOLLECTION instead of null for empty inputs, improving
  null-safety in downstream SQL.
• Floating Point: Minor precision differences in ST_Centroid and ST_Area due to different
  underlying math implementations (verified via tolerance checks).
• Vertex Ordering: Polygons are now normalized to standard winding (e.g., Clockwise for exterior rings) during serialization, which may change the order of vertices returned by ST_Points.

Release notes

(x) Release notes are required, with the following suggested text:

## Geospatial
  * Replace ESRI geometry library with JTS for improved ecosystem compatibility. ({issue}`issuenumber`)
  * WKT parsing is now stricter per OGC standards and rejects previously accepted invalid syntax. ({issue}`issuenumber`)
  * `ST_Union` edge case changes: empty inputs return empty geometry collection instead of null, and point-on-line unions no longer insert vertices at intersection points. ({issue}`issuenumber`)