[PART-1] Figure and Shape Parser support (#4681)

Fix geography validation bugs, replace ad-hoc CLR binary metadata parsing with spec-compliant implementation, and fix polygon Valid flag in properties byte.

**Currently**, Babelfish has the following issues in `spatialtypes.c`:

1. **Geography accepts out-of-range longitude values.** `geography::Point(45, 20000, 4326)` succeeds silently. T-SQL enforces longitude bounds of −15069 to +15069 degrees and rejects this input.

2. **Geometry/geography accepts Infinity coordinates.** Binary data containing `±Infinity` coordinate values passes all validation because only `isnan()` is checked, not `isinf()`. T-SQL rejects both NaN and Infinity.

3. **CLR binary metadata (Figure/Shape arrays) is parsed incorrectly.** The old `check_geom_end_metadata()` reads 4 bytes at a time across 5-byte figure entry boundaries. It works only because the attribute byte happens to produce the expected uint32 value when the following offset bytes are zeros. No bounds checking exists on metadata reads.

4. **Polygon properties byte missing Valid flag.** Babelfish outputs `0x00` for valid 2D polygons while T-SQL outputs `0x04` (V flag set). Linestrings already handled valid/invalid variants correctly.

5. **`set_dimension_flag()` prematurely guesses geometry type.** Properties byte `0x04` was hardcoded as `LINE_TYPE`, creating a latent bug where valid polygons from T-SQL would be misidentified.

**With this change:**

1. New `validate_longitude_range()` and `validate_not_inf_nan()` functions added and integrated into all validation paths (text input, binary input, direct point creation). Geography objects with longitude outside ±15069° are now rejected.

2. `check_nan_coordinates()` now checks both `isnan()` and `isinf()`. All geography validation paths also check for infinity.

3. New `parse_figures_and_shapes()` replaces `check_geom_end_metadata()`. Reads figure entries as 1+4 bytes and shape entries as 4+4+1 bytes per the T-SQL CLR spec (sections 2.1.3–2.1.4). Includes `CHECK_METADATA_BOUNDS` macro for buffer safety. Geometry type determined from Shape type byte — the single authoritative source.

4. Added `VALID_POLYGON_2D` through `VALID_POLYGON_3DM` constants. `determine_geom_dimensions()` now uses `is_valid` for polygons, matching the existing linestring pattern.

5. `set_dimension_flag()` no longer guesses `LINE_TYPE` for `0x04`. Falls through to `COMPLEX_GEOM_2D`, letting `parse_figures_and_shapes()` determine the actual type from Shape metadata.

6. `geography_from_bytea()` returns NULL for SRID = −1 input instead of crashing on length validation.

### Issues Resolved

- Geography silently accepts longitude values outside ±15069° range
- Geometry/geography silently accepts ±Infinity coordinates
- CLR Figure metadata parsed by reading 4 bytes across 5-byte entry boundaries (works by coincidence)
- CLR Shape metadata not parsed at all (geometry type guessed from byte patterns)
- Polygon properties byte missing Valid flag (byte 5 mismatch with T-SQL)
- `set_dimension_flag()` hardcodes `LINE_TYPE` for properties byte `0x04` (latent bug for valid polygons)
- NULL geography (SRID = −1) causes crash instead of returning NULL

### Test Scenarios Covered ###
* **Use case based -**
  - Point: 2D, 3DM, Empty (geometry)
  - LineString: 2-point, multi-point, Empty (geometry)
  - Polygon: invalid 2D, invalid 3D, invalid multi-ring, valid 2D, valid 3D, valid 3DM, self-intersecting, Empty (geometry)
  - Geography: Point, LineString, single-ring Polygon
  - Round-trip: geometry → varbinary → geometry for polygon

* **Boundary conditions -**
  - `geography::Point(45, 15069, 4326)` — longitude at positive boundary, must succeed
  - `geography::Point(45, -15069, 4326)` — longitude at negative boundary, must succeed
  - `geography::Point(90, 0, 4326)` — latitude at boundary, must succeed

* **Arbitrary inputs -**
  - 3-ring polygon (exterior + 2 interior rings)
  - Valid polygon (proper square) to verify V flag in properties byte
  - Self-intersecting polygon (invalid geometry)

* **Negative test cases -**
  - `geography::Point(45, 20000, 4326)` — longitude out of range, must error
  - `geography::Point(45, -20000, 4326)` — negative longitude out of range, must error
  - `geography::STGeomFromText('LINESTRING(0 0, 20000 45, 1 1)', 4326)` — longitude in linestring, must error
  - `geography::Point(91, 0, 4326)` — latitude out of range, must error
  - `CAST(0x00000000010C000000000000F07F0000000000004940 AS geometry)` — Infinity coordinate, must error
  - `CAST(0x00000000010C000000000000F87F0000000000004940 AS geometry)` — NaN coordinate, must error
  - `CAST(0xFFFFFFFF AS geography)` — SRID = −1, must return NULL

* **Minor version upgrade tests -**
  N/A — no catalog or protocol changes

* **Major version upgrade tests -**
  N/A — no catalog or protocol changes

* **Performance tests -**
  N/A — validation adds negligible overhead (one extra isinf() call per coordinate, one memcpy for longitude extraction)

* **Tooling impact -**
  N/A — no changes to tooling

* **Client tests -**
  N/A — no client protocol changes

Task: BABEL-6377
Signed-off-by: Gopal Verma <gopalgv@amazon.com>

Author: Gopalverma062

contrib/babelfishpg_common/src/spatialtypes.c

@@ -217,14 +217,14 @@ SELECT CAST(0xE6100000010403000000000000000000F03F000000000000084000000000000014
 GO
 ~~ERROR (Code: 33557097)~~
 
-~~ERROR (Message: Unsupported geometry type)~~
+~~ERROR (Message: Error converting data type varbinary.)~~
 
 
 SELECT CAST(0xE6100000010403000000000000000000F03F000000000000084000000000000014400000000000001C40000000000000104000000000000001000000010000000001000000FFFFFFFF0000000002 as geography)
 GO
 ~~ERROR (Code: 33557097)~~
 
-~~ERROR (Message: Unsupported geometry type)~~
+~~ERROR (Message: Error converting data type varbinary.)~~
 
 
 -- Test with Invalid bytes
@@ -237,9 +237,10 @@ GO
 
 SELECT CAST(0xE6100000010903000000000000000000F03F000000000000084000000000000014400000000000001C400000000000001040000000000000144001000000010000000001000000FFFFFFFF0000000002 as geometry)
 GO
-~~ERROR (Code: 33557097)~~
-
-~~ERROR (Message: Unsupported geometry type)~~
+~~START~~
+geometry
+E6100000010D03000000000000000000F03F000000000000084000000000
+~~END~~
 
 
 SELECT CAST(0xE610000001180000000000000840000000000000144000000000000000400000000000001040 as geography)
@@ -251,9 +252,10 @@ GO
 
 SELECT CAST(0xE6100000010903000000000000000000F03F000000000000084000000000000014400000000000001C400000000000001040000000000000144001000000010000000001000000FFFFFFFF0000000002 as geography)
 GO
-~~ERROR (Code: 33557097)~~
-
-~~ERROR (Message: Unsupported geometry type)~~
+~~START~~
+geography
+E6100000010D03000000000000000000F03F000000000000084000000000
+~~END~~
 
 
 -- When SRID is above 999999 for geometry 

test/JDBC/expected/Test-Linestring-vu-verify.out

@@ -0,0 +1,143 @@
+
+
+DROP TABLE  geometryAsVarcharpolygon
+
+DROP TABLE  geographyAsVarcharpolygon
+
+DROP TABLE  CharAsgeometrypolygon
+
+DROP TABLE  CharAsgeographypolygon
+
+DROP TABLE  VarCharAsgeometrypolygon
+
+DROP TABLE  VarcharAsgeographypolygon
+
+DROP TABLE  GeoVarCharAsgeometrypolygon
+
+DROP TABLE  GeoVarcharAsgeographypolygon
+
+DROP VIEW DimOfGeometrypolygon
+
+DROP VIEW AreaOfGeometrypolygon
+
+DROP VIEW TextFromGeometrypolygon
+
+DROP VIEW BinaryFromGeometrypolygon
+
+DROP VIEW SridFromGeometrypolygon
+
+DROP VIEW EmptyGeometrypolygon
+
+DROP VIEW ValidGeometrypolygon
+
+DROP VIEW ClosedGeometrypolygon
+
+DROP VIEW DisjointTempGeompolygon
+
+DROP VIEW DistanceTempGeompolygon
+
+DROP VIEW IntersectsTempGeompolygon
+
+DROP VIEW ContainTempGeompolygon
+
+DROP VIEW EqualsTempGeompolygon
+
+DROP VIEW equals_opgeompolygon
+
+DROP VIEW notequal_opgeompolygon
+
+DROP VIEW DisjointTempGeompolysr
+
+DROP VIEW DistanceTempGeompolysr
+
+DROP VIEW IntersectsTempGeompolysr
+
+DROP VIEW EqualsTempGeompolysr
+
+DROP VIEW ContainTempGeompolysr
+
+DROP VIEW equals_opgeompolysr
+
+DROP VIEW notequal_opgeompolysr
+
+DROP TABLE  geometryToByteapolygon
+
+DROP TABLE  geometryAsVarbinarypolygon
+
+DROP TABLE  CharAsVarbinaryGeompolygon
+
+DROP TABLE  VarbinaryAsgeometrypolygon
+
+
+DROP VIEW DimOfgeographypolygon
+
+DROP VIEW AreaOfgeographypolygon
+
+DROP VIEW TextFromgeographypolygon
+
+DROP VIEW BinaryFromgeographypolygon
+
+DROP VIEW SridFromgeographypolygon
+
+DROP VIEW Emptygeographypolygon
+
+DROP VIEW Validgeographypolygon
+
+DROP VIEW Closedgeographypolygon
+
+DROP VIEW DisjointTempGeogpolygon
+
+DROP VIEW DistanceTempGeogpolygon
+
+DROP VIEW IntersectsTempGeogpolygon
+
+DROP VIEW ContainTempGeogpolygon
+
+DROP VIEW EqualsTempGeogpolygon
+
+DROP VIEW DisjointTempGeogpolysr
+
+DROP VIEW DistanceTempGeogpolysr
+
+DROP VIEW IntersectsTempGeogpolysr
+
+DROP VIEW EqualsTempGeogpolysr
+
+DROP VIEW ContainTempGeogpolysr
+
+DROP VIEW equals_opgeogpolygon
+
+DROP VIEW notequal_opgeogpolygon
+
+DROP VIEW equals_opgeogpolysr
+
+DROP VIEW notequal_opgeogpolysr
+
+DROP VIEW PolygonGeogFromText
+
+DROP VIEW PolygonGeomFromText
+
+DROP TABLE  geographyToByteapolygon
+
+DROP TABLE  geographyAsVarbinarypolygon
+
+DROP TABLE  CharAsVarbinaryGeogpolygon
+
+DROP TABLE  VarbinaryAsgeographypolygon
+
+
+DROP TABLE geospatialpointgeom_polysr
+
+DROP TABLE GEOSPATIALPOLYGONGEOM_dt
+
+DROP TABLE GEOSPATIALPOLYGONGEOM_INVALID_dt
+
+DROP TABLE GEOSPATIALPOLYGONGEOG_INVALID_dt
+
+DROP TABLE geospatialpointxgeog_polysr
+
+DROP TABLE GEOSPATIALPOLYGONGEOG_dt
+
+DROP TABLE GEOSPATIAL_POLYGEOMRCV_dt
+
+DROP TABLE GEOSPATIAL_POLYGEOGRCV_dt