[SEDONA-457] Don't write GeometryUDT into org.apache.spark.sql.parquet.row.metadata when writing GeoParquet files

[Kontinuation]

Did you read the Contributor Guide?

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

Is this PR related to a JIRA ticket?

• Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-457. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?

Spark SQL primarily uses org.apache.spark.sql.parquet.row.metadata to infer the schema of parquet files. It will fall back to using the native parquet schema only when org.apache.spark.sql.parquet.row.metadata is absent. Writing the schema of dataframes with GeometryUDT columns into org.apache.spark.sql.parquet.row.metadata may cause compatibility problems. Please refer to the JIRA ticket for more details.

This patch replaces the GeometryUDT written into the metadata with binary type, since this is the physical data type for representing geometry values.

How was this patch tested?

Add assertions to verify that the metadata written by Spark SQL does not contain GeometryUDT.

Did this PR include necessary documentation updates?

• No, this PR does not affect any public API so no need to change the docs.

[jiayuasu]

This PR will fix OvertureMaps/data#89