Filter entities in the UI (part 9): Support / in queries

[abey79]

Related

• Closes Properly support / in filter queries #8903
• 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
  • Filter entities in the UI (part 4): Add entity filtering in the blueprint tree #8706
  • Filter entities in the UI (part 5): Add snapshot tests for the blueprint tree #8728
  • Filter entities in the UI (part 6): Refactor re_blueprint_tree and add more tests #8795
  • Filter entities in the UI (part 7): Refactor and optimize re_time_panel and add more tests #8863
  • Filter entities in the UI (part 8): Make the query semantics more powerful #8886
  • Filter entities in the UI (part 9): Support / in queries #8933

What

This PR supports / in filter query. Semantics are now as follows:

• Queries are made of whitespace separated keyword.
• Paths are not matched unless they match all keywords individually at least once.
• Keywords may have 1 or more / separated "parts".
• Single part keyword behave as before: paths are matched if they contain that keyword anywhere at least once.
• Single part keyword can now be prefixed and/or postfixed with a slash, eg. "/fir". In that case, the keyword part must be found at the beginning and/or end of at least one path part to match (e.g. "/fir" matches "/my/first/entity" but doesn't match "xxfire/entity").
• Multi-part keyword (e.g. "a/b/c") match paths that contains corresponding, matching sequence of part (e.g. "/xxxxa/b/cxxxxx"). Such keywords can also be prefixed and/or postfixed with a "/", with the same semantics.

[github-actions]

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

• I have tested the web viewer

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

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

[Wumpf]

pre-approved with comments during a call-based review.

absolutely love this, both result & execution

[abey79]

Quick benchmark session

Blueprint panel

Test: air traffic data, default blueprint, add/maximize empty view (no time rendering), collapse time panel

query	main	this PR
none	0.8ms	0.8ms
"a"	1.0ms	2.3ms
"aft/0"	n/a	1.1ms

Notes:

• 3 views where all entities are present, so big tree.
• "a" yields a lot of result

Time panel

Test: air traffic data, no view, uncollapse all in time panel

query	main	this PR
none	0.4ms	0.5ms
"a"	0.6ms	1.2ms
"aft/0"	n/a	0.6ms