Address known issues of mouse target

[helgoboss]

Known issues:

• "Move cursor to/by": Fast repeated invocations can actually result in less distance because the OS doesn't process each movement. Ideas:
  • Don't report the actual mouse position as current value but the last set one.
  • Throttle
• "Move cursor to/by": Using a high-res fader with "Make relative" seems to do pretty large steps even if invoked very softly.
• "Turn scroll wheel": Appeared to have a similar issue when turning fast as with moving the cursor. Investigate.
• macOS: Simulating a drag works on REAPER's faders but not on REAPER's circular controls (but using wheel scroll simulation should be preferred anyway because the mouse cursor doesn't leave its initial position - not all plug-ins make sure the mouse cursor stays at position)
• macOS: Not having "Accessibility" privilege granted will make ReaLearn panic (device_query crate issue)
• Windows: When using "Move cursor to" with Y axis, the cursor doesn't stay on the same X coordinate. Better use "Move cursor by" for the time being.

Originally posted by @helgoboss in https://github.com/helgoboss/realearn/issues/686#issuecomment-1253570238

[m-malandro]

I'm on Windows 10 and I'm experiencing mouse drift with "Move cursor to" for both X and Y axes. See the gif here:

https://stash.reaper.fm/v/46931/Mouse%20Drift.gif

Thanks!