Also remove nested inclusions when removing a subtree

[jleibs]

What

• Resolves: Clicking "-" to remove entity doesn't work if children were included explicitly #5690

Introduce new helper method that not only adds an exclusion but also removes all the current matches within the subtree.

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
• If applicable, add a new check to the release checklist!

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

[emilk]

I think it would be wise to also remove the old foot-gunny add_entity_exclusion, or rewrite it to never include the subtree (i.e. take an entity path instead of a EntityPathRule)

[jleibs]

I considered it, but I found the behavior that it gives in the query editor-view to still be useful.

In that view we give much clearer visibillity into all the rules that are in effect and the fact that 1 click = 1 rule modification matches what a user also does when hand-editing the expressions, where I would expect them to manually delete the inclusion lines rather than having them deleted automagically once they've typed a subtree removal expression.