[Tracking]: Lightspeed receiver support

OpenLogi uses the existing Unifying-compatible HID++ path for supported Lightspeed and Nano receivers. Support is added by receiver PID, so this issue tracks which PIDs are recognised and which devices have been tested.

## Receiver coverage

| PID | Family | Device | Status |
| -------------------------------------- | ---------- | -------------------------- | ------------------------------ |
| `c52b`, `c532` | Unifying | Multiple devices | Supported |
| `c537` | Nano | G602 | #684 open; hardware test needed |
| `c548` | Bolt | Multiple devices | Supported |
| `c53f` | Lightspeed | G305 | Supported by #388 |
| `c539` | Lightspeed | G903 LS | Supported by #510 |
| `c547` | Lightspeed | G502 X LIGHTSPEED | Supported; tested in #459 |
| `c53a`, `c53d`, `c541`, `c545`, `c54d` | Lightspeed | No confirmed device report | Not tested |

## PR status

| PR | State | Main work |
| ---- | ------ | ---------------------------------------------- |
| #351 | Open | Multiple Lightspeed PIDs and RGB effects |
| #369 | Open | G305 support with extra gaming-mouse features |
| #388 | Merged | `c53f` receiver recognition |
| #459 | Open | Onboard profiles, tested with a G502 X |
| #510 | Merged | `c539` receiver recognition |
| #684 | Open | G602 Nano receiver `c537` recognition |

## Current direction

The merged receiver work routes Lightspeed and Nano receivers through the existing Unifying-compatible path. A separate route type is not needed unless real hardware shows different protocol behaviour.

Receiver names can still be shown as Lightspeed or Nano in the UI without changing the route.

## Still needed

- [ ] Test #684 with a real G602. Logitech lists its Nano receiver as [`046d:c537`](https://support.logi.com/hc/en-ca/articles/360023307694-Logitech-G602-Wireless-Gaming-Mouse-Technical-Specifications).
- [ ] Confirm devices and hardware behaviour for `c53a`, `c53d`, `c541`, `c545`, and `c54d`.
- [ ] Check #462, which was reported as Bolt even though the mouse uses Lightspeed.
- [ ] Add a Lightspeed option to `device_support.yml` and update its outdated receiver wording.

Related but separate: #392 is a wired device, #461 tracks device artwork, and gaming-mouse features are tracked separately.

Start with device_support.yml and the existing receiver recognition work referenced in #388, #510, and #684. Check the remaining receiver PIDs and test the G602 support in #684 with real hardware, then verify the Lightspeed entry and receiver wording are updated. Done means the listed devices and PIDs have confirmed support or test status.

Written by the indexing model from the issue text.