feat(geo): add geometry data type

[ariesdevil]

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

Summary

Initial support geometry type. We use EWKB for serialize geo data and use EWKT for display geo data.

part of #14543

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 

[cdmikechen]

Each type of Geometry has a different definition, and there seems to be a difference in the type definitions used.
We have recently in learning related content, geo-arrow has given more specifically the type of description: https://github.com/geoarrow/geoarrow/blob/main/format.md

In addition, postgis, for example, also has a good guide to the use and definition of each type declaration:
https://postgis.net/workshops/postgis-intro/geometries.html

geom geometry(multilinestring, 3857) 

Hope these will be helpful to the improvement of this PR. And if there's anything I can do to help, let me know.

[kkk25641463]

Geometry have many types. Each type has own memory layout which is described in geoarrow spec . I think we will import geoarrow-r craft and define GeometryType as below:

#[derive(Debug, Clone, PartialEq, Eq)]
pub struct GeometryType<T: Geometry>;

pub type GeometryPointType = GeometryType<GeoDataType::Point>;
pub type GeometryLineStringType = GeometryType<GeoDataType::LineString>;
pub type GeometryLargeLineStringType = GeometryType<GeoDataType::LargeLineString>;
pub type GeometryPolygonType = GeometryType<GeoDataType::Polygon>;
pub type GeometryLargePolygonType = GeometryType<GeoDataType::LargePolygon>;
pub type GeometryMultiPointType = GeometryType<GeoDataType::MultiPoint>;
pub type GeometryLargeMultiPointType = GeometryType<GeoDataType::LargeMultiPoint>;
pub type GeometryMultiLineStringType = GeometryType<GeoDataType::MultiLineString>;
pub type GeometryLargeMultiLineStringType = GeometryType<GeoDataType::LargeMultiLineString>;
pub type GeometryMultiPolygonType = GeometryType<GeoDataType::MultiPolygon>;
....

[ariesdevil]

Hi @cdmikechen @kkk25641463 , thanks for your interest in this feature. We will follow the snowflake approach to deal with GEO types.
https://docs.snowflake.com/en/sql-reference/data-types-geospatial

Support geoparquet not planed. cc @cdmikechen

Support sub-types for geo type is not our approach now, since databend is a snowflake alternative we will follow it's way, related PR is closed. cc @kkk25641463

BTW: I'll plan to use geozero to read/store wkb binary data, if you have better options, please feel free to make suggestions.

[drmingdrmer]

Add a new version and a corresponding test:
https://github.com/datafuselabs/databend/blob/0c05f068eaa20fb05899b71b0852a3e5f24252e9/src/meta/proto-conv/src/util.rs#L110

[drmingdrmer]

Reviewed 6 of 50 files at r2, 5 of 26 files at r3.
Reviewable status: 10 of 61 files reviewed, 13 unresolved discussions (waiting on @ariesdevil, @b41sh, @kkk25641463, and @sundy-li)

[cdmikechen]

@ariesdevil
Hi~ I'm glad this PR has been merged into the latest databend. So far I have found that there is still one problem that has not been solved:
Should we need to rename st_makepoint to st_makegeompoint or st_geom_point ?

[ariesdevil]

@cdmikechen
We follow snowflake’s naming rules

[cdmikechen]

@cdmikechen We follow snowflake’s naming rules

Here are snowflake documents:
https://docs.snowflake.com/en/sql-reference/functions/st_makegeompoint
https://docs.snowflake.com/en/sql-reference/functions/st_makepoint

If we want to return a geometry point, should we use st_makegeompoint ?

[ariesdevil]

@cdmikechen We follow snowflake’s naming rules↳

Here are snowflake documents: https://docs.snowflake.com/en/sql-reference/functions/st_makegeompoint https://docs.snowflake.com/en/sql-reference/functions/st_makepoint↳

If we want to return a geometry point, should we use st_makegeompoint ?↳

Yep, I'll fix it in next PR, thanks figure it out。