Fix Ogre2 CPU ray queries from inside AABBs

[Dylan-Gallagher]

🦟 Bug fix

Fixes #1226.

Summary

Ogre returns a broadphase distance of zero when a ray starts inside an object's axis-aligned bounding box. The Ogre2 CPU ray-query path discarded all candidates with a distance less than or equal to zero, so it never ran the triangle-level intersection pass for those objects.

This change keeps zero-distance candidates while continuing to reject negative distances. The narrowphase still determines whether the ray actually intersects the geometry.

The regression test uses a rotated box whose AABB contains the ray origin while the box geometry does not. Before the fix, the CPU ray query reports no result. After the fix, it returns the expected front-face intersection, object ID, distance, and point.

Backport Policy

• This is safe to backport to the following versions:
  • Jetty
  • Ionic
  • Harmonic
  • Fortress
• This should not be backported
• I am not sure
• Other (fill in yourself)

Validation

• Final regression on Ogre and Ogre2 GL3Plus: 4/4 CTest entries passed.
• Full serial CTest suite under Xvfb: 257/257 passed.
• codecheck: cpplint and cppcheck targets passed.
• Negative control: changing the production condition back to <= 0.0 makes RayQueryTest.RayOriginInsideObjectBounds fail because the result is empty.

Checklist

• Signed all commits for DCO
• Added a screen capture or video to the PR description that demonstrates the fix (not needed for this CPU query regression)
• Added tests
• Updated documentation (not needed; no public API or documented behavior changed)
• Updated migration guide (not needed; no migration impact)
• Consider updating Python bindings (not needed; no API change)
• codecheck passed (See contributing)
• All tests passed (See test coverage)
• Updated Bazel files (not needed; no files or targets were added)
• While waiting for a review on your PR, please help review another open pull request to support the maintainers
• Was GenAI used to generate this PR? If so, make sure to add "Generated-by" to your commits. (See this policy for more info.)

Generated-by: OpenAI Codex (GPT-5; accessed 2026-08-18)

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by and Generated-by messages.

Backports: If this is a backport, please use Rebase and Merge instead.