layoutGrabColumn crash (grabWindow is null) when Google Chrome starts on Wayland, leaving stale input grab

[aramge]

Describe the bug

When Google Chrome is launched on Wayland, PaperWM crashes in layoutGrabColumn
with TypeError: can't access property "title", grabWindow is null. The window is
not tiled into the scrollable band. As a side effect, a stale input grab is left
active, making mouse clicks non-functional in the affected window until the PaperWM
extension is restarted.

Cannot reproduce on PaperWM 49.0.0 / GNOME 49.4 / Kernel 6.12.85.
Was reproducible on the previous installation (PaperWM < 49, Kernel 6.19.x).
Filing for documentation purposes and to help identify which change fixed it.

To Reproduce

1. Run GNOME Shell on Wayland with a PaperWM version prior to 49.0.0
2. Launch Google Chrome (google-chrome-stable)
3. Observe: Chrome does not appear in the PaperWM window band
4. Observe: Mouse clicks on Chrome tabs do not register
5. Run gnome-extensions disable paperwm@paperwm.github.com && sleep 1 && gnome-extensions enable paperwm@paperwm.github.com
6. Observe: Chrome appears in band, clicks work again

Expected behavior

Chrome is tiled into the PaperWM band normally. If the window cannot be tiled,
no input grab should be left open.

Error from journalctl