Feat: Add explicit container options for GeoJSON outputs

[dyrpsf]

Overview
This PR implements the TODO noted in _h3shape.py regarding allowing users to specify strict GeoJSON containers when converting cells to geometries.

Changes Made
Updated h3shape_to_geo to accept a container argument. By default, it retains the 'auto' behavior (returning the simplest valid Polygon or MultiPolygon). However, it now supports wrapping the output into specific GeoJSON structures:

• MultiPolygon (safely wraps a standard Polygon)
• Feature
• FeatureCollection
• GeometryCollection

This is particularly useful for downstream pipelines (like mapping libraries or databases) that require strict schema enforcement, such as always expecting a FeatureCollection even if the query only returns a single cell.

cc: @jongbinjung, @dfellis, @isaacbrodsky

[isaacbrodsky]

Thanks - the implementation looks good to me.

Could you add some tests to demonstrate this?

[dyrpsf]

Thanks - the implementation looks good to me.

Could you add some tests to demonstrate this?

Thanks @isaacbrodsky! I've added a suite of unit tests in tests/test_geojson_containers.py to verify all the new wrapper formats. I also resolved the trailing whitespace issue that was tripping up ruff in the CI pipeline. Let me know if you need anything else!

[dfellis]

@dyrpsf unfortunately after approving the test suite run, not only is the linter still failing, but there are failing tests, as well: https://github.com/uber/h3-py/actions/runs/29942829160/job/89001681729?pr=495#step:8:510

[dyrpsf]

@dyrpsf unfortunately after approving the test suite run, not only is the linter still failing, but there are failing tests, as well: https://github.com/uber/h3-py/actions/runs/29942829160/job/89001681729?pr=495#step:8:510

Thanks for the heads-up, @dfellis! I see the failed checks for both the linter and the test suite. I'm reproducing the errors locally right now so I can track down exactly what broke. I'll have a fix pushed shortly!

[dyrpsf]

Hey @dfellis, I just force-pushed the fixes! I added the explicit ValueError logic for invalid/insufficient containers, handled the exact-match scenario, and added unit tests to verify the behaviour. I also resolved the formatting issues so ruff is passing. Since I don't have permissions to trigger the CI workflows, could you please hit 'Approve and run' when you get a chance? Thanks!

[dfellis]

Hey @dfellis, I just force-pushed the fixes! I added the explicit ValueError logic for invalid/insufficient containers, handled the exact-match scenario, and added unit tests to verify the behaviour. I also resolved the formatting issues so ruff is passing. Since I don't have permissions to trigger the CI workflows, could you please hit 'Approve and run' when you get a chance? Thanks!

Was asleep when you sent that. Just triggered it.

[dfellis]

@dyrpsf so @ajfriend was very strict when he set up this repo :) https://github.com/uber/h3-py/actions/runs/29986675613/job/89269426447?pr=495#step:8:38

The test suite passes, but now it's no longer 100% code coverage, so you need more tests.