[Bug]: Cannot add MX Vertical using dongle

### Pre-flight checklist

- [x] I searched [existing issues](https://github.com/AprilNEA/OpenLogi/issues?q=is%3Aissue) and this is not a duplicate.
- [x] I am on the [latest release](https://github.com/AprilNEA/OpenLogi/releases/latest) or a recent `master` build.
- [x] I quit **Logi Options+** before running OpenLogi (the two apps fight over HID++ access and only one can own a receiver at a time).

### Which part of OpenLogi?

GUI (desktop app)

### OpenLogi version

0.4.1

### Operating system

macOS

### OS version & architecture

26.5.1, M5 Pro

### Device model

MX Vertical

### How is the device connected?

Logi Bolt receiver

### Affected area(s)

- [x] Device discovery / detection
- [ ] Button remapping
- [ ] DPI control
- [ ] SmartShift
- [ ] Per-application profiles
- [ ] Battery status
- [ ] Settings / configuration (TOML)
- [ ] Auto-update
- [ ] Menu bar / tray
- [ ] Other

### What happened?

When I want to add my MX Vertical I am using via the USB dongle, it does not show app. There is no pairing mode for the dongle, switching the mouse to pairing mode would connect it via bluetooth which I do not want.

### Steps to reproduce

Try to add a mouse via USB dongle.

### `openlogi list` output

```text

```

### Logs

```shell

```

### macOS permissions (if applicable)

- [x] OpenLogi has **Accessibility** permission (needed to remap buttons via the event tap).
- [x] OpenLogi has **Input Monitoring** permission (needed for Bluetooth-direct devices and capture).

Reproduce the issue in the OpenLogi GUI with an MX Vertical connected through a Logi Bolt USB receiver, then trace the device discovery path used when adding a mouse. Compare the receiver-based discovery behavior with the documented Bluetooth path and use `openlogi list` while checking relevant logs. Done means the MX Vertical appears and can be added through the USB receiver without requiring Bluetooth pairing.

Written by the indexing model from the issue text.