[DRAFT][Geo][SQL] Enhance SRID/CRS support based on PROJ data

[uros-db]

What changes were proposed in this pull request?

Extends Spark's Spatial Reference System (SRS) support to 10000+ entries sourced from the PROJ library's EPSG
and ESRI databases, substantially improving the breadth of GeometryType and GeographyType support.

Why are the changes needed?

Currently, Geometry and Geography types offer only limited SRID support (a few hardcoded values).

Does this PR introduce any user-facing change?

Yes, 10000+ additional SRID/CRS values are supported for geospatial types.

How was this patch tested?

Updated the corresponding unit tests for SRS mapping.

Was this patch authored or co-authored using generative AI tooling?

Yes, Claude 4.6 Opus.

[mkaravel]

Given that the intent here is that we override an existing value, I think it would be best to throw an error if existing is null. Something like:

if (existing == null) {
  throw new RuntimeException("SRID " + srid + " should have already been registered");
}
SpatialReferenceSystemInformation ogcEntry =
    new SpatialReferenceSystemInformation(srid, ogcStringId, existing.isGeographic());
sridToSrs.put(srid, ogcEntry);
stringIdToSrs.put(ogcStringId, ogcEntry);
stringIdToSrs.put(existing.stringId(), ogcEntry);

[mkaravel]

I think it makes more sense to do this inside the SpatialReferenceSystemCache.java and geo_utils.py instead of here. I believe it is cleaner that the data generated by this script map completely to what we get from Proj.