fix(macOS): cursor_position returns incorrect position

[wusyong]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes
• No

Checklist

• This PR will resolve monitor::cursor_position() not displaying correct cursor position #707
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary
• It can be built on all targets and pass CI/CD.

Other information

[wusyong]

@amrbashir I've test it and the coordinates should be correct now.
But I found #708 is true, all platforms return logical positions. We'll need to discuss how to fix this.

[amrbashir]

what do you mean by logical exactly? not relative to the window top-left corner? because CursorMoved is relative to the window top-left corner, while window.cursor_position() and event_loop.cursor_position() get the cursor position in the global space.

[wusyong]

I mean window.cursor_position() and event_loop.cursor_position() will return logical position. I have a monitor with physical size 2880x1800 and with scale factor 2. Both current_position() will return 1440x900 if I point to the bottom right of the screen. I can test further on Linux and Windows later, but they don't convert with scale factor when returning either.

Anyway, this discussion should move to #708. This PR should fix correct coordinate in second monitor (excluding scale factor).