Verify Win-key forwarding over RDP and VNC

[btsouth]

Test whether the focus-scoped Win-key hook follows the active remote session and QEMU window correctly. Confirm Ctrl+Alt+G works as the fallback and document any differences between RDP and VNC.

[btsouth]

The RDP path is now verified, including focus-scoped Windows/SUPER forwarding. Leaving this open for VNC coverage and a direct Ctrl+Alt+G fallback check.

[btsouth]

Some findings from testing this locally, before anyone spends time on the remote side.

The Windows shortcut leak users were hitting was not focus related. The launcher was dying after about 33 minutes (#17), and once it is gone every Windows shortcut goes back to Windows. Worth retesting RDP and VNC on a build with that fix, otherwise it will look like a remote session problem.

With the window genuinely foreground, Win alone, Win+R and Win+Tab were all correctly swallowed and Win+Space reached Omarchy. Win+L locked the host anyway, and that one is not fixable, Windows handles it above the low level hook chain.

One thing that is still worth checking here: while the window is not foreground the hook correctly passes the Windows key through, which looks identical to the bug from the user's side. If a remote client steals focus in ways we do not expect, that is the failure mode to look for.