Introduce the GeoLineStrings archetype and support it in the map view

[abey79]

What

☝🏻 title

• New GeoLineStrings archetype, using a new GeoLineString component
• Support it in the map view
• Fix heuristics for the map view: now a $origin = / single view will be spawned whenever a single GeoXXX entity exists anywhere.
• Snippets and screenshot for GeoPoints
• Snippet for GeoLineStrings (but not screenshot, blocked on Add round join to line strips #829)
• Added some types to rerun.hpp
• Fixed/copy/pasted LineStrip2D edit ui for GeoLineString
• Add python unit tests for GeoPoints
• Add python unit tests for GeoLineStrings

Switzerland boundaries according to a couple of AIs and an official source:

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using examples from latest main build: rerun.io/viewer
  • Using full set of examples from nightly build: rerun.io/viewer
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
• If applicable, add a new check to the release checklist!
• If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

• PR Build Summary
• Recent benchmark results
• Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

[github-actions]

Deployed docs

Commit	Link
50b4991	https://landing-5is26iekl-rerun.vercel.app/docs

[emilk]

I feel very uneasy with an interface that doesn't explicitly spell out the order of latitude and longitude for all our map primitives, consider this has been the source of bugs for so many years for so many people