More rigorious evaluation of visualizable entities in spatial views using new SpatialTopology store subscriber

[Wumpf]

What

• Important part of Re-engineer the space-view heuristics engine #4388

Introduces a SpatialTopology support structure which is built incrementally using a store subscription.
It is geared towards replacing the existing SpaceInfo (todo!).

The first usecase for this is a more rigorous determination of visualizable entities for spatial views: this now allows us to much more accurately reason about what entities are visualizable and how to treat corner cases (/invalid cases) like logged pinhole under a pinhole.

Since this makes the evaluation of visualizable entities / creation of their context a bit more complex in some scenes, this comes with a bit of a perf regression during heuristic eval. However, since the topology changes rarely and deterministically, this also brings a big opportunity for only evaluating the more complex context objects when needed and even sharing them accross different space view (candidates). This is not included in this pr since this comes with the open question of where to store such a secondary cache (likely on topology) and how to flush it (probably best for any new entity or new relevant component).

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 newly built examples: app.rerun.io
  • Using examples from latest main build: app.rerun.io
  • Using full set of examples from nightly build: app.rerun.io
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

• PR Build Summary
• Docs preview
• Examples preview
• Recent benchmark results
• Wasm size tracking

[jleibs]

Let's not change it yet but this continues to make me think these entities should just be in primary_space.entities in the first place so we don't have to mutate the set.

[Wumpf]

yeah we can totally throw the responsibility for this onto the space topology, just need to add a few more unit tests that it does the right thing under updates.
Nice thing is that unlike the old SpaceInfo we know what we're dealing with and who's the "target audience"