Add ASUS Aura 0x1B29 detector

[Komzpa]

Initial commit for ASUS Aura USB controller 0x0B05:0x1B29.

This adds PID 0x1B29 for the ASUS ROG Strix LC III cooler RGB controller. The device uses the same ASUS Aura USB protocol as the already-supported mainboard controllers, so this reuses the existing AuraMainboardController protocol implementation while registering the physical device as ASUS ROG Strix LC III instead of another motherboard PID.

I verified this on Linux with real hardware:

• USB ID: 0b05:1b29
• HID path: /dev/hidraw1
• serial reported by OpenRGB: 9876543210
• detected by this branch as ASUS ROG Strix LC III
• exposed modes: Direct, Off, Static, Breathing, Flashing, Spectrum Cycle, Rainbow, Chase Fade, Chase
• exposed zones: Aura Addressable 1

Tested commands on the device:

# openrgb --noautoconnect --list-devices
4: ASUS ROG Strix LC III
  Type:           Motherboard
  Description:    ASUS Aura USB Mainboard Device
  Version:        HID: /dev/hidraw1
  Location:       HID: /dev/hidraw1
  Serial:         9876543210
  Modes: [Direct] Off Static Breathing Flashing 'Spectrum Cycle' Rainbow 'Chase Fade' Chase
  Zones: 'Aura Addressable 1'

# openrgb --noautoconnect --device 4 --mode off
# openrgb --noautoconnect --device 4 --mode static --color 000000
# openrgb --noautoconnect --device 4 --mode direct --color 000000

The controller class still reports the existing mainboard category/description because this patch intentionally keeps the change small and reuses the known-good protocol implementation. If maintainers prefer, I can split a dedicated RGBController wrapper for the cooler label/category in a follow-up.

Build verification:

• Built the full project in a clean debian:sid Docker container with qmake OpenRGB.pro && make -j$(nproc).

Checklist for Accepting a Merge Request for a New Device

• The source branch of the merge request is not protected (master is protected by default when creating a fork, so it is recommended to not use it as your source).
• The New Device issue raised for this device is linked to this MR with a keyword Closes / Resolves / Implements
• There is a device protocol page in the Developer Wiki or there is enough information / captures in the New Device issue to provide ongoing support.
• The code to be merged follows the style guide and change requirements as documented in the contributing guide.

• Meta data for the device is included in RGBController_* file
• This device is detected and is working on Windows 10 and / or 11
• This device is detected and is working on Linux: Debian forky/sid-derived system, kernel-side HID path /dev/hidraw1
• Logging for Info, Warnings and Errors has been added for troubleshooting purposes