fix(shortcuts): surface globalShortcut.register failures (linux/wayland)
Two diagnostic improvements for the "shortcuts broken on Linux"
report. We can't repro on darwin, so this is groundwork: make the
next Linux-side investigation see exactly what's failing.
- `registerGlobalShortcut` now logs `requested`, the platform-
translated `accelerator`, and `process.platform` when
`globalShortcut.register` returns false. Wayland compositors
often refuse the grab silently — without the accelerator string
in the log it was hard to correlate with WM-reserved bindings
(e.g. `Alt+Space` in GNOME).
- `tile:shortcuts:register` now checks the return value of
`registerGlobalShortcut` and replies with the error on the
caller's `replyTopic`. Previously the error was dropped on the
floor and the caller assumed registration succeeded.
The local-shortcut fallback in `app/cmd/background.js` (registering
the same hotkey as both global and local) is unchanged. The
remaining "local shortcuts also broken on Linux" leg of the bug
needs hands-on Linux to triage — most likely candidates are the
WM/compositor swallowing the keypress before `before-input-event`
fires or a `process.platform` branch elsewhere; both require a
Linux Electron run to confirm.