Multidevice query silently drops Android hosts: no afk bucket, so buildMultideviceHostParams skips them

[ErikBjare]

Follow-up to #969, which made the multidevice query use the actual …-synced-from-<host> bucket IDs (verified: fixes "There's no bucket named 'aw-watcher-window_erb-main3'" on an instance with aw-sync data).

What still fails

buildMultideviceHostParams (src/util/multidevice.ts) requires both bucketsWindow(host)[0] and bucketsAFK(host)[0]; otherwise the host is skipped with only a console.warn. Android devices sync aw-watcher-android-synced-from-<host> (type currentwindow) and aw-watcher-android-unlock-synced-from-<host> (type os.lockscreen.unlocks) — there is no afkstatus bucket, so every phone is dropped from the multidevice view with no UI indication. Erik's instance after importing the POCO F8 Ultra: 1.4M events present, none in the multidevice query.

Suggestion

• For hosts with a currentwindow bucket and no afkstatus bucket, derive the afk series from the os.lockscreen.unlocks bucket when present (the phone is "not-afk" between an unlock and the next lock), or run the window bucket without an afk filter when neither exists — the Android single-device view already does the latter.
• Surface the skip in the UI ("N devices skipped: no AFK data") instead of only in the console.

cc @TimeToBuildBob

[TimeToBuildBob]

PR #988 fixes this by routing Android-only hosts through the android query path instead of skipping them.

The key changes:

• buildMultideviceHostParams accepts an optional bucketsAndroid lookup; hosts with no window+afk pair fall back to the android bucket (same path the single-device Android view uses, no afk filter)
• canonicalEvents emits not_afk = []; for Android/ScreenTime params so the multidevice union never references an undefined variable
• iOS ScreenTime imports (aw-import-screentime_ prefix) are detected automatically
• 4 new tests covering the android fallback, iOS detection, desktop-preferred-over-android, and the android query path in multideviceQuery