Moonlander keyboard uses dev22

For any users, this works and logs to stdout (replace `-` with your filepath to log to a file):

```sh
sudo logkeys -s --no-daemon -o - -d event22 --timestamp-every
```

```
I: Bus=0003 Vendor=3297 Product=1969 Version=0111
N: Name="ZSA Moonlander Mark I"
P: Phys=usb-0000:03:00.0-2.3/input0
S: Sysfs=/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-2/1-2.3/1-2.3:1.0/0003:3297:1969.000B/input/input34
U: Uniq=0
H: Handlers=sysrq kbd event22 leds
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f
```

I can attach more if needed, but wanted to avoid listing out all my devices if knowing them isn't necessary.

Start by reproducing the reported command with a ZSA Moonlander Mark I on Linux, using the listed event22 device path and checking stdout output. Review how logkeys selects and reads keyboard event devices; done should mean the Moonlander is handled correctly without requiring an unspecified workaround.

Written by the indexing model from the issue text.