Configure existing ROS 2 robots from device discovery

[temiroff]

Outcome

• inspect the live ROS 2 graph during Add Robot to Device
• select the existing ROS 2 provider when odometry or LiDAR interfaces are present
• pass confirmed topics/capabilities to the device-side Hardware configurator
• preserve serial discovery as the fallback for direct servo-bus robots
• pin merged blacknode-robot 0.5.3 commit 7528d637fe661bc628d86765c65d82b2a0d5050a

Safety

• ROS discovery is read-only
• the provider publishes no ROS messages and exposes no motion/arm operations
• ROSOrin vendor services and startup configuration remain untouched

Verification

• python -m pytest tests/test_editor_devices.py -q (142 passed)
• PYTHONPATH=python python -m unittest discover -s tests (566 passed, 8 skipped)
• editor npm run build (passed)
• blacknode-robot package CI passed in PR Deploy workflows to paired devices #32

Managed Runtime release decision

No blacknode-runtime release is required. The device behavior is supplied by merged blacknode-robot 0.5.3 through the managed Hardware package surface; this PR updates the merged Hardware source pin used by Devices -> Software -> Check updates -> Update all. The orchestration change is editor-server-only.