fix: use lossy UTF-8 conversion for device sysname to avoid panic

[neuralbroker]

The sysname() method used to_str().expect() which panics when a USB device's kernel sysname contains non-UTF-8 bytes. Use to_string_lossy() instead, matching the behavior of the name() method.

Fixes pop-os/cosmic-epoch#2105 where cosmic-comp crashes with:
Device sysname is no valid utf8: Utf8Error { valid_up_to: 126, error_len: Some(1) }

[PolyMeilex]

Can you prove that this is indeed true? That string is most likely controlled by the kernel or udev rather than by the device.

The linked issue describes a different problem, the panic log you provide does not align with the one in that issue, what's the source of it?

Something similar to running libinput debug-events and getting a dump of its outputs should be enough to prove that the described device can indeed control its sysname string. Alternatively, one can also dump /sys/class/input/, /sys/class/sound/, etc. contents to prove that one of the files there contains a non-ascii filename.

[neuralbroker]

Ill check on that once again