Spotted by Rémi Bernon.

Due to the asynchronous nature of Wayland events, and the design of the
xdg_toplevel protocol, an xdg configure event may be a reaction to a
request in the application's configuration past, and the size hint may
be out of date. For example:

1. The client commits a 100x100 buffer to a surface.
2.1 The compositor sends xdg configure(100x100, state=activated).
2.2 In the meantime, the client resizes and commits a 50x50 buffer.
3. The client receives the event from (2.1). If we respect the
   size hint, we will resize back to 100x100, although this was
   neither the client's nor the compositor's intention.

To mitigate this we ignore size hints for states that do not
require strict size adherence.

Take into account the window scale factor and use wp_viewport to
instruct the compositor to present cursors with that scale.

Take into account the window scale factor and use wp_viewport to
instruct the compositor to present surfaces at that scale.

Introduce and use functions to convert between the window logical and
Wayland surface coordinate spaces. At the moment the two are the same
but this will change with the introduction of scaling support.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55660

Assume that the window rect passed NtUserIsWindowRectFullScreen is
expressed in terms of thread dpi and convert monitor rects accordingly
for proper matching.

Handle Wayland keyboard events and translate them to Windows events,
currently using a hardcoded US key mapping.

Fixes: bb6bcaf8

This partially reverts commit 0b7eed03.