Filter entities in the UI (part 4): Add entity filtering in the blueprint tree

[abey79]

Related

• Part of Project: filtering entities in the UI (first iteration) #8586
• Part of a series of PR:
  • Filter entities in the UI (part 0): Make CustomContent more useful #8645
  • Filter entities in the UI (part 1): Introduce a filter widget #8652
  • Filter entities in the UI (part 2): Introduce entity filtering in the time panel #8654
  • Filter entities in the UI (part 3): Move action to a menu in the blueprint panel and keep default blueprint when using heuristics #8672
  • ...

What

This PR implements entity filtering in the blueprint tree.

In important design principle applied here is that the filtering applies only on the visible part of items. This has two major consequence:

• The prefix of the data result entity path that matches the view origin is not considered in matching, because it is also not displayed in the tree. (That applies to non-projected data results.)
• The sub-tree defined by the view origin is ignored when matching projected entities, because that sub-tree is not displayed either ($origin placeholder in the tree).

Snapshot tests for this is coming in the next PR

blueprint-tree-filter.mp4

[github-actions]

Web viewer built successfully. If applicable, you should also test it:

• I have tested the web viewer

Result	Commit	Link	Manifest
✅	ff14c1d	https://rerun.io/viewer/pr/8706	+nightly +main

^{Note: This comment is updated whenever you push a commit.}

[Wumpf]

looking great, love those new tests as well
the nˆ2 behavior in the search is a bit concerning but we talked about this already (more refactors following which may be able to address this along the way)