fix(annotations): reliable simulator element highlighting

[lauridskern]

Summary

Fixes several problems that made the iOS simulator annotation tool unreliable. Also changes the default layout so only iOS opens when both platforms have a running device.

• No highlights at all: CoreSimulatorBridge can lose its accessibility connection after backboardd and SpringBoard restart. Every describe-ui read then returns no accessibility data. Baguette.describeUi now restarts the bridge (launchctl kickstart) and retries once, at most every 10 s per device.
• Only coarse elements in Expo Go: Metro targets were matched by app name. Expo Go's name ("Expo Go") never matches its bundle ID (host.exp.Exponent), so React Native inspection was skipped. When no name matches on the device, the iOS simulator's foreground bundle ID is used as an exact match.
• Offset highlights on card stacks: hit-testing picked the smallest element at a point regardless of paint order, so the slightly inset next card in a stack won over the visible one. Image, text or SVG painted later in another branch now hides earlier React Native elements at that point.
• Highlights a few points off near the bottom right: the bezel definition describes a 400×872 pt screen cutout for a 402×874 pt iPhone. Inspection now returns the accessibility root's screen size through a typed readTree result, and the store rescales the capture and any in-progress pointer state to it.
• Both platforms opening: with an iOS simulator and an Android device both running, the panel now opens iOS only, as docs/devices.md describes. The platform select can still show both.

Commits are split per fix. The final commit bumps the version to 0.1.139.

Telemetry

• New ios.accessibility_bridge.restarts count with a fixed outcome (recovered, unavailable, failed). Failed restarts also report a handled simulator.accessibility_bridge error. Documented in docs/telemetry.md.
• Existing ui.annotations.inspection, ui.annotations.tree_processing and ui.annotations.runtime_available still cover the changed inspection and hit-testing paths. No new identifiers or content are sent.

Testing

• New tests cover the bridge restart and its rate limit, the Expo Go foreground match (mismatched app, failed lookup, name match skipping the lookup), card-stack occlusion, a later transparent overlay not hiding content, and the 400→402 screen correction including in-progress drags.
• npm test: 605 pass. 7 tests fail the same way on main (public release, Android CLI and packaged CLI, owned startup).
• tsc reports no new errors; two existing errors in inspection-tools.ts are gone.
• Checked live on an iOS 27 iPhone 18 Pro simulator running an Expo Go app:
  • accessibility recovered after restarting the bridge
  • Expo Go matched its Metro target
  • the hidden card was picked at 0 of 11,430 sampled points (previously 10,554)
  • hover hit-testing takes about 7 µs
  • the server reports a 402×874 screen