[Bug]: Can't install on rpm-ostree (e.g. Fedora Silverblue)

### 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?

Both

### OpenLogi version

0.7.1

### Operating system

Linux

### OS version & architecture

Fedora Linux 44 (Silverblue)

### Device model

MX Master 3

### How is the device connected?

Other / not sure

### Affected area(s)

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

### What happened?

I'm trying to install OpenLogi on Fedora Silverblue, an rpm-ostree based OS, and the postinstall script breaks on trying to run udevadm.

rpm-ostree(openlogi.post)[95511]: Failed to send reload request: No such file or directory

To work around this, I found an example in the [wireshark.spec](https://src.fedoraproject.org/rpms/wireshark/blob/rawhide/f/wireshark.spec#_207) that runs udevadm only if `/run/udev/control` is a socket. Could this be added?

### Steps to reproduce

rpm-ostree install ./openlogi-v0.7.1-linux-amd64.rpm

### Diagnostics report

```markdown

```

### `openlogi list` output

```text

```

### Logs

```shell

```

### macOS permissions (if applicable)

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

Start with the RPM package's postinstall script and reproduce the failure using `rpm-ostree install ./openlogi-v0.7.1-linux-amd64.rpm` on Fedora Silverblue. Compare its udevadm handling with the linked wireshark.spec example, and consider the issue complete when installation no longer fails because `/run/udev/control` is absent while regular installations retain their expected behavior.

Written by the indexing model from the issue text.