Query caching for pinhole querying in transform context

[Wumpf]

What

• Missed this one on Cached transforms & disconnected spaces for faster scenes with many transforms #5221

Didn't make a big difference in perf though for the scene I tested with (opf --no-frames), but no point in not keeping it, likely more relevant for more even more pinholes.

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]

Why not change the implementation of query_pinole to use the cache instead?

[Wumpf]

ripples too much right now and didn't want to have that in this PR.
Actually many callsites of query_pinhole only want to know about whether the component exist, so they shouldn't do the full query (go to EntityTree instead!)