feat: add stac-geoparquet reading and writing

[gadomski]

Related Issue(s):

• Closes Use stacrs to read+write stac-geoparquet #1455

Description:

• Add stacrs as an optional dependency and use it to read and write item collections
• I initially thought about embedding it into StacIO but that felt too impactful, since we're just doing ItemCollections for now
• It's a little awkward since stacrs is async, so we may want to refactor some stuff out to helper functions if we end up using it other places

PR Checklist:

• Pre-commit hooks pass (run pre-commit run --all-files)
• Tests pass (run pytest)
• Documentation has been updated to reflect changes, if applicable
• This PR maintains or improves overall codebase code coverage.
• Changes are added to the CHANGELOG. See the docs for information about adding to the changelog.

[codecov]

Codecov Report

Attention: Patch coverage is 71.42857% with 6 lines in your changes missing coverage. Please review.

Project coverage is 91.44%. Comparing base (542b9fb) to head (8984e84).

Files with missing lines	Patch %	Lines
pystac/item_collection.py	71.42%	5 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1521      +/-   ##
==========================================
- Coverage   91.47%   91.44%   -0.04%     
==========================================
  Files          54       54              
  Lines        7542     7560      +18     
  Branches      915      917       +2     
==========================================
+ Hits         6899     6913      +14     
- Misses        457      459       +2     
- Partials      186      188       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gadomski]

Marking as draft while I dig into some PyPI size restrictions that are keeping me from releasing Windoze wheels that work.

[jsignell]

At first read I don't love the idea of adding another "how to read" flag. I feel like that is really what stac_io is meant for - this kind of messes up the existing patterns. Like how would you go about defining a different way to read from geoparquet?

On the other hand I guess adding stacrs here will make reading from geoparquet work in the pystac-client case as well even thought that one uses a different stac_io. So maybe this is a practical solution.

[gadomski]

Yeah, I don't love it either — it's the complexity of "STAC but in different formats" bleeding into our software implementation. I'll have a think.