Improve device deployment UI

[temiroff]

What changed

• names local and remote deployments from the active workflow tab, with Deployed graph as the Untitled fallback
• presents an active deployment hardware lease as a healthy informational state instead of an error
• replaces stale armed-state display with deployment motion-control ownership
• separates paired devices and remote deployments into responsive cards
• keeps the add-node menu and action buttons usable in smaller windows
• improves responsive behavior for the main toolbar and deployment controls

Why

A running robot was shown with a red hardware-monitor error and Armed: No even though the deployment correctly owned and controlled it. Deployment names also fell back to Current graph, and several controls could be clipped in compact windows.

Impact

Operators can distinguish healthy deployment ownership from actual hardware failures, identify deployments by workflow name, and use device/deployment controls at narrow viewport sizes.

Validation

• python -m pytest tests/test_editor_devices.py -q — 32 passed
• PYTHONPATH=python python -m unittest discover -s tests — 387 passed, 8 skipped
• cd editor && npm run build — passed