feat(query): implement ST_YMAX/ST_XMIN/ST_YMIN

[kkk25641463]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

feat: Implement ST_YMAX/ST_XMIN/ST_YMIN with issues

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[kkk25641463]

And more code clean:

1. With geozero srid issues resolved in version 0.13.0. The srid was get from geos struct.
2. Geozero project maintainer believes that displaying SRID=0 is meaningless in the realm of spatial information. So test case with srid=0 is not display with geozero lib.

[kkk25641463]

The implementation of the st_transform function has been affected by the static linking of georust/proj. Although it seems like fixed in the main branch, the release cycle of the proj project spans years. Additionally, support for z/m coordinates in georust/geo has also long lacked organized discussions and reviews by maintainers. Given this situation, can we consider incorporating these two projects into the mainline code of Databend for maintenance?Once the georust community's feature mature, we will switch back to using the community libraries.

[b41sh]

The implementation of the st_transform function has been affected by the static linking of georust/proj. Although it seems like fixed in the main branch, the release cycle of the proj project spans years. Additionally, support for z/m coordinates in georust/geo has also long lacked organized discussions and reviews by maintainers. Given this situation, can we consider incorporating these two projects into the mainline code of Databend for maintenance?Once the georust community's feature mature, we will switch back to using the community libraries.

Hi @kkk25641463 You can merge with the commit id first, and then change back when the upstream repository code is merged.