feat(editor): the three-dot button in the simulation too

A tap on a device in the simulation now also chooses it, so its three-dot
button shows as in the design, wherever the simulation's menu offers
something (the desktop, each card's data exchange; a switch has none).
Java's action of the tap stays (desktop, switch and NAT tables), a tap
beside lets go. The device sheet stays closed — the design is locked — and
the others see no frame. Java opens that menu only with a right click.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

packages/editor/browser/shared.spec.ts

@@ -130,6 +130,9 @@ test('three people in one project of F: moving, reading only, one simulation for
   // Both have the notebook's desktop open: each sees the other's dot on it.
   await expect(desktop(mia, notebook).locator(`[data-watcher="${benUser}"]`)).toBeVisible();
   await expect(desktop(ben, notebook).locator(`[data-watcher="${miaUser}"]`)).toBeVisible();
+  // Their taps chose the notebook too (its three-dot button), but in the simulation that is no frame for the others —
+  // told in the same message as the open desktop just seen.
+  for (const page of [mia, ben]) await expect(page.locator('rect.chosen-by')).toHaveCount(0);
   // Rita may look, not type; she sees both on the desktop, and they see her.
   const ritas = await commandLine(rita, notebook);
   await expect(desktop(rita, notebook).locator('[data-watcher]')).toHaveCount(2);