Fix geojson EllipsoidRhumbLine error for duplicated points

[jjspace]

Description

Sometimes polygons have duplicated points in their definition. This causes the code we have to subdivide the lines for the EllipsoidRhumbLine arc type to fail. Even if it's not ideal the duplicated points shouldn't cause our render to crash, especially when other applications like geojson.io render correctly and validators show nothing wrong with the GeoJSON.

Note: I'm not 100% confident this fix is done at the right "level" of the code. I was also able to get the failing examples working by removing the error call itself. That said I think it's a valid error if you're using that class directly but in this instance for polygons we simply don't care and can short circuit the function before we even try the code that "fails".

For context I encountered this during work on #12456 with one of the example sources

Issue number and link

Fixes #7864

Testing plan

• Test these local sandcastles in main and this branch and check that this branch does not crash out
  • Country outlines from GeoJSON crashes in Cesium #7864
  • Vineyard from sample data from Support OGC API - Features #12456 (if it 404s just try reloading)

Author checklist

• I have submitted a Contributor License Agreement
• I have added my name to CONTRIBUTORS.md
• I have updated CHANGES.md with a short summary of my change
• I have added or updated unit tests to ensure consistent code coverage
• I have updated the inline documentation, and included code examples where relevant
• I have performed a self-review of my code

[github-actions]

Thank you for the pull request, @jjspace!

✅ We can confirm we have a CLA on file for you.

[ggetz]

Nice, this is a long running bug that I'm sure many will love to see fixed. Thanks @jjspace!

I just have one comment about how we can make this fix a bit more general-purpose. Please update CHANGES.md and look into adding a unit test at least for this case.

I don't think we have any tests for subdivideRhumbLine specifically, so some additional coverage would also be welcome. 😄

[ggetz]

All looks good to me! I can confirm several of the example datasets from the original issue are now rendering without error 🎉

[ggetz]

Thanks @jjspace!