[FEAT] Add simple-features geometry type and initial operations

[amitschang]

After discussion with @desmondcheongzx in #3017, I thought it might be worthwhile to open a PR for this work I've done making a (e)wkb backed geometry type representing "simple-features" geometries. Basically it implements a logical Geometry type whose physical backing is the validated (e)wkb bytes. This method incurs cost in serde upon operations, but enables earlier and potentially wider support for geo operations (due to existing library support) and supports collections and non-uniform geometries - so should have use before and even after native types would be added.

Here are included encoding/decoding (wkt/wkb) and a number of operations within the "geo" expression namespace to demonstrate combinations of unary/binary to bool/float/geometry, but is not meant to be in any way complete.

There are more examples in the discussion linked above, but very briefly what it looks like:

d = daft.from_pydict({'p1': ['POINT(0 0)', 'POINT(1 1)', 'POINT(0 1)'], 'p2': ['POINT(0 0)']*3})
d = d.with_column('p1g', d['p1'].geo.decode()).with_column('p2g', d['p2'].geo.decode())
d.select('p1', 'p2', d['p1g'].geo.distance(d['p2g']).alias('dist'), 'p1g').sort('dist').collect()
╭────────────┬────────────┬────────────────────┬────────────╮                                                                                 
│ p1         ┆ p2         ┆ dist               ┆ p1g        │                                                                                 
│ ---        ┆ ---        ┆ ---                ┆ ---        │                                                                                 
│ Utf8       ┆ Utf8       ┆ Float64            ┆ Geometry   │                                                                                 
╞════════════╪════════════╪════════════════════╪════════════╡                                                                                 
│ POINT(0 0) ┆ POINT(0 0) ┆ 0                  ┆ <Geometry> │
├╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┤
│ POINT(0 1) ┆ POINT(0 0) ┆ 1                  ┆ <Geometry> │
├╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┤
│ POINT(1 1) ┆ POINT(0 0) ┆ 1.4142135623730951 ┆ <Geometry> │
╰────────────┴────────────┴────────────────────┴────────────╯

There are probably a number of missing/wrong things in here, and some organizational improvements that could be made (daft-geo crate?), and docs - but may be a start 😄

[codspeed-hq]

CodSpeed Performance Report

Merging #3061 will not alter performance

_{Comparing amitschang:geotype (3b7a1ec) with main (1aaf3cf)}

Summary

✅ 17 untouched benchmarks