fix(ayaneo): leave joystick lighting to Steam Customization

[sknowledge1]

InputPlumber currently discovers the AYANEO 3 joystick rings as LED source devices, which competes with the selected Steam Customization path. This removes only the legacy and current LED entries from the AYANEO 3 profile; gamepad, IMU, DMI and composite options are preserved.

Rebased on InputPlumber v0.82.0 / d951ef9df713a3ad3a88645a8c07b79ea5592274, with one profile-only commit: 1470feb548920e1609d3a614e4ccc692bf1f1195. No RGB D-Bus API or new ownership exception is introduced.

OGC #123 supplies the kernel interfaces. The exact one-file patch applies to the pinned source, and preserved profile sections and the GitHub diff have been checked.

Private device checks on 2026-10-14 used an AYANEO 3 8840U, BIOS 1.00, official Bazzite 44.20261012.1 / kernel 7.2.9-ogc3.1.fc44.x86_64 and Steam 1791918634. The candidate profile was bound into the canonical service's namespace; its effective SHA256 a9358f40bb0c19e07404808a92d079caa17fbc1f3bad1fbc17a820a9d4de1631 was verified and it contains no LED source entries. The existing generic permission rule makes brightness, multi_intensity and effect writable as the Steam user. The user confirms controller input after module release/refit, Decky restart, real suspend/resume and reboot. The IMU profile is preserved; physical motion input was not independently exercised.

Steam Customization has no joystick lighting controls with the stock generic LED name. The compiled/loaded OGC go:rgb:joystick_rings candidate also fails discovery after a Steam restart; Steam's native LEDManager reports service unavailable and no devices. The stock driver is restored. Removing InputPlumber LED ownership alone is not demonstrated to enable Steam lighting, so this profile must not ship alone as a completed lighting path.

The user explicitly chose to keep Steam lighting and wait for support. Keep this draft pending working Steam discovery/effects/persistence and coordinated official Bazzite package/image acceptance. The optional managed lighting proposal remains paused.

Assisted-by: Codex:GPT-6

[pastaq]

There is no reason to remove this. The Dualsense target can write colors to the interface.

[sknowledge1]

noted - thanks.