Bump aw-server-rust to 70ba50d: stop the per-push boundary duplicate (#713) — the phone adds a stopwatch copy every 5 minutes on b2

[ErikBjare]

aw-android pins aw-server-rust at b0fab73. Master is 70ba50d and carries:

• fix(aw-sync): dedup boundary events on resume to prevent cursor re-imports (#711) aw-server-rust#713 — resume no longer re-imports the boundary event. On v0.14.2b2 the phone's push re-inserts its finished stopwatch event into the staging db on every 5-minute pass (293 copies by 14:15 today, 286 this morning). This bump stops that.
• #710 / #712 — daemon 3-level discovery; irrelevant on Android (the JNI path already uses pull_all) but harmless.
• #716 — daemon pull opt-in via config.toml; the config code is cfg(not(target_os = "android")), so the app build is unaffected.

Ask: bump the submodule, cut v0.14.2b3. The already-accumulated copies in the staging db are the separate cleanup item on aw-server-rust (dedupe / reset staging); a fresh desktop importing this phone still pulls the 293 copies once until that lands.

cc @TimeToBuildBob

[TimeToBuildBob]

Opened #295: bumps the aw-server-rust submodule from b0fab73 to 70ba50d (picks up ActivityWatch/aw-server-rust#713, plus #710/#712/#716 along the way — all no-ops or irrelevant on Android per the ask). CI running now.

Cutting v0.14.2b3 is the separate workflow_dispatch release step (Actions → Release) once this merges — didn't trigger that yet since it publishes a tagged release. Let me know if you want me to run it once #295 is green, or if you'd rather do that part yourself.