shell32/tests: Move tests of IExplorerBrowser_SetFolderSettings() to a separated function and more tests.

Only pre-win7 systems return E_INVALIDARG for invalid values, and only pre-vista
systems accept FVM_AUTO as a view mode, others fall it back to FVM_ICON. Let's
switch to modern behaviours, so that we don't need additional code for handling
that when using it to implement IExplorerBrowser_SetFolderSettings().

server: Return STATUS_IMAGE_MACHINE_TYPE_MISMATCH when the mapping's machine differs from the process.

Based on a patch by Nikolay Sivov.

Based on a patch by Nikolay Sivov.

Based on a patch by Nikolay Sivov.

Otherwise Gecko keeps it running when it is created via put_classid, and
it leaks everything due to holding a ref to it.
Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

When the plugin host is created, its only ref is being held by the element
it is associated with.
Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Currently this worked by luck because it is leaking; the element holding
it never releases it.
Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

The new test doesn't pass, but it doesn't crash either, and that's
enough to fix the WinZip installer.

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

lparam != 0 does not imply lparam_size is big enough for a MSG, so we
can end up manipulating memory past the end of the buffer.
Co-authored-by: Jacek Caban <jacek@codeweavers.com>

Update the desktop window size to match the current virtual screen rect.

Use a driver internal window message to dispatch updates to display devices from
the desktop window thread.

Store all incoming Wayland output state as pending and make it current
in a thread-safe way when the "done" event arrives. This enables other
threads, with proper locking, to safely read consistent and complete
Wayland output information.

Handle Wayland output events sent after process initialization,
and update the win32u display devices when handling these
events in the desktop window process.

Create a dedicated thread from which we read and dispatch Wayland events
(beyond the initial ones).

There is currently no benefit to dynamic allocation, and static
allocation allows us to simplify some aspects of initialization.