fix: respect run dependencies on sibling outputs for build ordering

[esteve]

This PR fixes a regression in the topological sort that was introduced during the v0.58.0 refactor. When multiple recipes are built together, the dependency graph used for ordering builds only considered pin_subpackage references from run dependencies, but ignored plain run: specs. This caused solver failures when a package needed a plain runtime dependency that hadn't been built yet.

The fix replaces extract_dependency_names with extract_dependency_names_with_sibling_context, which also collects plain run/run_constraints dependencies whose names match other outputs in the build set.

This issue is causing ROS Humble to fail a full rebuild for the RoboStack project RoboStack/ros-humble#400 (ros-humble-uncrustify-vendor which is a plain run dependency was scheduled to build after its consumer ros-humble-ament-uncrustify), with this fix I was able to do a full rebuild of ROS Humble.

I found this fix as part of an existing Claude session 780ce80, I don't know what's the policy regarding AI-generated contributions, so I kept the author (Claude) and removed the skip filtering test as it's not part of this fix, but part of 8f5cb03

[pb01ka]

Overall I found the fix correct and the tests also seem to be meaningful.

The main actionable item from my end is removing the Option<> wrapper from sibling_names since the other path is never executed as of today. Hence, it would make the contract clearer and removes a branch that can never execute.

[pb01ka]

Submitting approval.

@wolfv I think this can be merged.

Thank you.