update dataflow-gamepad to drive the arm instead of the bench

It now runs joy, teleop and dora-ulite6 with the probe declared and the
console shut, so a pad can be checked against the arm that will actually
move. ROBOT_IP in both arm dataflows points at the bench arm.

The run recipe drops dora up + dora start: dora 1.0.1 refuses to start a
dataflow holding git: nodes from a coordinator, reporting that no build was
run straight after one that succeeded. That costs the file dora topic, which
needs a coordinator to read the wire.

dataflow-robot.yml

@@ -16,8 +16,8 @@
 # then looks for its entrypoint in this dataflow's venv instead. README.md has the
 # detail. `dataflow.yml` has no `git:` nodes and is fine with --uv.
 #
-# Set ROBOT_IP and TOOL_TYPE below to match the arm in front of you. The
-# defaults are `dora-ulite6`'s own: 192.168.1.192 and a vacuum tool.
+# ROBOT_IP and TOOL_TYPE below name the arm in front of you: the bench arm at
+# 192.168.1.162, with a vacuum tool.
 #
 # The web console comes with the node: it serves the page and holds the
 # browsers' sockets itself, so `http://<this machine>:7000` is a second way to
@@ -102,7 +102,7 @@ nodes:
       tcp_pose: std/core/v1/Float32
       robot_state: std/core/v1/String
     env:
-      ROBOT_IP: "192.168.1.192"
+      ROBOT_IP: "192.168.1.162"
       TOOL_TYPE: "vacuum"
       # The outermost deadman, enforced by the controller whether or not any of
       # this is alive. Every timer above must stay below it.