Fix a bug where an incorrect 3D space view origin could be suggested

[abey79]

What

Fix a bug introduced in #5411 and #5423 where the wrong origin would be suggested when creating a 3D space view from an entity part of a 2D space view. Quoting the original PR:

For 3D space views: the origin of the subspace that contains the selected entities common ancestor, or, if that one is rooted on a pinhole, the origin of the parent sub-space. Further, if a ViewCoordinate is logged in between the subspace origin and the common ancestor, then it's used as suggested origin. In most case, that means /, unless a DisconnectedSpace is encountered.

The part of that logic where we check for a ViewCoordinate in the parent subspace was implemented incorrectly, which resulted in check_context_menu_suggested_origin to fail. With this PR, this test now passes.

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

[Wumpf]

ah subtle! good find and fix