[GH-3260] GeoPandas: Implement distributed geom_equals_identical

[jiayuasu]

Did you read the Contributor Guide?

• Yes, I have read the Contributor Rules and Contributor Development Guide.

Is this PR related to a ticket?

• Yes, and the PR name follows the format [GH-XXX] my subject.

Closes #3260.
Part of #2230.

What changes were proposed in this PR?

GeoPandas 1.1 added geom_equals_identical for exact structural comparison of
geometry values. Unlike topological equality or tolerance-based
geom_equals_exact, it compares geometry type, nesting, component and vertex
order, coordinate dimensionality, and every represented XY/Z/M ordinate. NaN
ordinates at the same position compare equal.

This PR adds the distributed GeoPandas API layer on top of the native
ST_EqualsIdentical predicate merged in #3266:

• Implement GeoSeries.geom_equals_identical(other, align=None) and delegate
  GeoDataFrame.geom_equals_identical through the active geometry column.
• Support scalar Shapely geometries, GeoSeries, GeoDataFrame, and
  pandas-on-Spark Series inputs.
• Preserve GeoPandas-compatible index alignment, including duplicate and
  MultiIndex values, positional comparison with align=False, result naming,
  non-nullable boolean output, null-to-false behavior, and CRS mismatch
  warnings.
• Execute comparisons with native Spark expressions; geometry rows and results
  remain distributed, and the plan contains no Python UDF execution.
• Preserve Z/M/ZM metadata for typed empty scalar values and retain Sedona's
  standalone LinearRing-to-LineString representation.
• Document the remaining representation boundaries and update the English and
  Chinese GeoPandas tutorials and release notes.

This is the final PR in the #3260 stack and is based directly on master. Its
prerequisites are merged:

• [GH-3260] Preserve M and ZM in Python GeometryUDT serialization #3265 preserves M and ZM when Shapely geometries cross the Python
  GeometryUDT boundary.
• [GH-3267] Preserve recoverable geometry dimensions #3268 preserves every coordinate layout recoverable by JTS at the compact
  Java SerDe boundary and rejects mixed layouts that a single-layout container
  cannot represent losslessly.
• [GH-3260] Add ST_EqualsIdentical across Sedona SQL engines #3266 provides ST_EqualsIdentical across Sedona's SQL engines.

The predicate compares the geometry representation it receives. JTS still
cannot distinguish ordinary XY from declared XYZ when every Z ordinate is NaN,
including empty XYZ values and zero-member collections. Direct Shapely inputs
with mixed layouts inside a Polygon or same-type multi-geometry may also be
normalized by Python GeometryUDT serialization before reaching the JVM. These
boundaries are documented in the public method.

How was this patch tested?

• Built the Spark 4.1.1 / Scala 2.13 shaded artifact with Java 17.
• GeoPandas 1.1.3 / Shapely 2.1.2 / GEOS 3.13.1 focused identity matrix:
  22 tests passed.
• GeoPandas 1.0.1 compatibility matrix: 19 tests passed and
  3 upstream-version-dependent tests skipped.
• Full affected GeoSeries and GeoPandas parity files: 427 tests passed and 1 skipped.
• Coverage includes scalar and Series inputs, XY/Z/M/ZM distinctions, typed
  empties, NaN ordinates, standalone rings, aligned and positional comparison,
  duplicate and MultiIndex values, CRS warnings, nulls, and serialization
  boundaries.
• Execution-plan coverage verifies that no Python execution nodes are added.
• Black, AST parsing, Markdown linting, the documentation build, repository
  hooks, and git diff --check passed.

Did this PR include necessary documentation updates?

• Yes, I am adding a new API. I am using the current SNAPSHOT version,
  v2.0.0.
• Yes, I updated the English and Chinese GeoPandas tutorials, public API
  documentation, and release notes.