Introduce new archetype for Axes3D

[jleibs]

What

• Builds on top of: Introduce ImagePlaneDistance Component #6505 (merge that first and rebase)

This replaces the axes-related entity properties with a new Axes3D archetype.

The archetype allows overriding the axis-length from code.
Controlling whether the axes are visible now happens via enabling of the visualizer.

We use similar heuristics to before to enable axes3d visualizers on transforms in certain situations.

The legacy UI has been remapped to the new indicator/heuristics implementation.

TODO:

• [] Still need to implement the example in rust / cpp.

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!

• 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
62c354a	https://landing-aid4jaaji-rerun.vercel.app/docs

[abey79]

proper link for web build: https://rerun.io/viewer/pr/6510?manifest_url=https://app.rerun.io/version/nightly/examples_manifest.json

[abey79]

Again, lots of this is way over my head, but lets not block that on Andreas being back to office :)

Curious about what you think is needed to make the switch to enabling override_ui for this space view (instead of using the feature flag) and remove the legacy UI entirely?

On that note, II wasn't able to add a AxisLength component override in the UI, other than by manipulating the legacy UI. Is that expected?

[emilk]

This PR seems to have broken CI: https://github.com/rerun-io/rerun/actions/runs/9436507239/job/25991550784

In particular, pixi run -e wheel-test RUST_LOG=debug python tests/roundtrips.py --release --target aarch64-unknown-linux-gnu --no-py-build fails with make: *** No rule to make target 'roundtrip_axes3d'.

It seems we don't run the roundtrip tests on each PR (understandable), but that means we miss adding roundtrip tests when we need them. We should have a fast CI job that only checks that we have roundtrip tests, without running them.

Fix coming in #6524