Mouse capture on unsupported OS is confusing

**Describe the issue**
I've recently tried an old linux distro (specifically Mandrake 8.2) which probably didn't have any support for vm mouse. I thought for days that the mouse wasn't actually being recognized by the old kernel as only the scrolling wheel and mouse buttons were being detected and the macOS mouse cursor was disappearing when hovering over guest display while the guest os cursor was stuck in the middle of the screen. I realized only a few days later that I actually needed to click on the input device capture button on UTM VM's title bar in order for the mouse movement to be recognized.

In my opinion the current solution is very confusing, as one sees the macOS cursor disappearing therefore expecting it to be captured by the guest. This leads the user into thinking the guest OS is actually the culprit therefore sending the user down the wrong rabbit hole.

I think a clean solution would be to avoid hiding the macOS cursor when the mouse isn't actually being captured by the guest or maybe to enable mouse capture on unsupported guest OS when one clicks over the guest display. I don't know if any of these ideas are feasible but I think I remember VMware Workstation capturing the mouse on unsupported OSes only when clicking into the guest VM, while it automatically detected mouse movement communication without forcing the mouse capture when the guest OS actually supported it.

**Configuration**
* UTM Version: 4.5.3 (99)
* macOS Version: 14.5 (23F79)
* Mac Chip (Intel, M1, ...): M1

**Crash log**
The app didn't crash.

**Debug log**
[debug.log](https://github.com/user-attachments/files/16257611/debug.log)

**Upload VM**
[config.plist.zip](https://github.com/user-attachments/files/16257619/config.plist.zip)