Allow clients to access the location of the mouse cursor

Wayland's security model currently blocks global hotkeys unless the compositor implements them, such as Hyprland does.

This also blocks grabbing the location of the mouse unless the window is currently focused.

I believe it would be appropriate to add a protocol that gives the x and y values of the mouse cursor globally, as little information can be grabbed from just the location of the mouse. As per @Zamundaaa's comment, I've rethought it, and settled on this:

Each display would be marked with its name, and resolution. The protocol would return the X and Y coords of the cursor on a display. For example: I have two displays, one of 1920x1080 (M1) and one of 1440x900 (M2); The protocol would take the screen name of the focused screen (M1 or M2 in this example), and return that alongside the coords of the cursor on that screen. I think this settles the issue about a global coordinate system.

IIRC, macOS and Windows have measures in place for keylogging but don't prevent cursor logging to the same extent, just to name a real world example.