wooting-udev-rules: add rules for Wooting 80HE

[justinas]

Description of changes

Adds udev rules for the newly released Wooting 80HE keyboard. I don't know much about the "gamepad mode", I'd welcome suggestions on whether it is applicable to 80HE and how to acquire the relevant IDs for these alternative modes.

Here's the relevant dmesg snippet (plugging in the keyboard in the default mode):

[  730.321286] usb 1-3.1: new high-speed USB device number 14 using xhci_hcd
[  730.488413] usb 1-3.1: New USB device found, idVendor=31e3, idProduct=1402, bcdDevice= 2.30
[  730.488419] usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  730.488421] usb 1-3.1: Product: Wooting 80HE
[  730.488422] usb 1-3.1: Manufacturer: Wooting
[  730.488424] usb 1-3.1: SerialNumber: A02B2431W08T00100S02H03975
[  730.540930] hid-generic 0003:31E3:1402.0010: hiddev97,hidraw1: USB HID v1.11 Device [Wooting Wooting 80HE] on usb-0000:0d:00.0-3.1/input0
[  730.552559] input: Wooting Wooting 80HE as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:07:00.0/0000:08:0c.0/0000:0d:00.0/usb1/1-3/1-3.1/1-3.1:1.1/0003:31E3:1402.0011/input/input26
[  730.628119] hid-generic 0003:31E3:1402.0011: input,hidraw2: USB HID v1.11 Keyboard [Wooting Wooting 80HE] on usb-0000:0d:00.0-3.1/input1
[  730.638601] hid-generic 0003:31E3:1402.0012: hiddev98,hidraw3: USB HID v1.11 Device [Wooting Wooting 80HE] on usb-0000:0d:00.0-3.1/input2
[  730.650562] input: Wooting Wooting 80HE System Control as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:07:00.0/0000:08:0c.0/0000:0d:00.0/usb1/1-3/1-3.1/1-3.1:1.3/0003:31E3:1402.0013/input/input27
[  730.702456] input: Wooting Wooting 80HE Consumer Control as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:07:00.0/0000:08:0c.0/0000:0d:00.0/usb1/1-3/1-3.1/1-3.1:1.3/0003:31E3:1402.0013/input/input28
[  730.702557] input: Wooting Wooting 80HE Mouse as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:07:00.0/0000:08:0c.0/0000:0d:00.0/usb1/1-3/1-3.1/1-3.1:1.3/0003:31E3:1402.0013/input/input29
[  730.702654] hid-generic 0003:31E3:1402.0013: input,hidraw4: USB HID v1.11 Mouse [Wooting Wooting 80HE] on usb-0000:0d:00.0-3.1/input3
[  730.713550] hid-generic 0003:31E3:1402.0014: hiddev99,hidraw5: USB HID v1.11 Device [Wooting Wooting 80HE] on usb-0000:0d:00.0-3.1/input4

Additionally: should we use the uaccess tag instead of the input group? I don't know much about udev, but that seems to be the recommended course of action nowadays, and it has a few usages in nixpkgs already.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.