[SEDONA-429][SEDONA-430] Support specifying GeoParquet spec version number and CRS

[Kontinuation]

Note: This PR depends on #1161

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-429 and https://issues.apache.org/jira/browse/SEDONA-430. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?

• Bumped the default GeoParquet version number from 1.0.0-beta.1 to 1.0.0
• Allow specifying GeoParquet version number using geoparquet.version option
• Allow specifying CRS metadata for geometry columns using geoparquet.crs option

How was this patch tested?

Add new tests for GeoParquet metadata.

Did this PR include necessary documentation updates?

• Yes, I have updated the documentation update.

[jiayuasu]

Can we add a new data source to only read the metadata of a parquet file? This is crucial for entry-level users to explore an unknown parquet file including geoparquet. In our geoparquet case, this will help user know the projjson value since we are not able to properly parse it to a known epsg code.

I understand that a Spark DataFrame only allows the schema to be the metadata which cannot be used to hold such information.

So I suggest that we add a new data source namely geoparquet.metadata, which loads these metadata using ParquetFileReader. One good example is from DuckDB: https://duckdb.org/docs/data/parquet/metadata.html

This can be addressed in a separate PR.

[jiayuasu]

Created a JIRA ticket for this: https://issues.apache.org/jira/browse/SEDONA-455

Let's address this in a separate PR.