Handle some spurious (?) warnings?

[brucecrevensten]

Two warnings show up in the stdout --

"UserWarning: The Shapely GEOS version (3.10.2-CAPI-1.16.0) is incompatible with the GEOS version PyGEOS was compiled with (3.10.1-CAPI-1.16.0). Conversions between both will be slow."

ShapelyDeprecationWarning: The array interface is deprecated and will no longer work in Shapely 2.0. Convert the '.coords' to a numpy array instead.

We are not convinced either of these are legit warnings - they may be a consequence of the ongoing Shapely development toward a 2.0 with tighter pyGEOS integration (see https://shapely.readthedocs.io/en/stable/migration.html). We could downgrade Shapely to 1.7 (unknown if/what impacts for other packages), shush the warnings, or leave them in place to address at a later time.

[brucecrevensten]

Shapely 2.0 is out but unclear if we'll be needing/using it after #270 is done?

[charparr]

Addressing #506 should also resolve this issue.

We might want to consider uv to handle our API dependencies

https://docs.astral.sh/uv/