FVWM by default uses a focus follow mouse model so the window under the mouse cursor automatically
gets focus. Windows explorer.exe and other windows managers use click to focus model. So on FVWM,
if a test changes the cursor position, it might affects other tests that rely on a specific focus
window. Restore the cursor position after sending simulating clicks to avoid affecting other tests
unintentionally. FVWM could be configured to use a click to focus model, but right now it will make
many tests starting to succeed and other tests fail. So it seems to be too big of a change. Flaky
is added to test_SetWindowPos() because this patch makes the tests succeed on Gitlab CI but the same
tests still fails for other window managers and on TestBots.

FVWM doesn't respect PPosition hints by default and tries to tile a window according to its rules.
This might break tests that require a window at a specific position. For example, when setting the
caption bar height to anything other than 18, some user32 tests start to fail. They succeeded
previously just because the caption bar and border height on FVWM totals to 18, which is happens to
be the same value used by Wine by default.

ntdll/tests: Handle another possible status when SystemProcessorFeaturesInformation is not supported.

The low word of the enumerated HKL is the desired user locale, the high
word is either the keyboard layout LANGID, or the keyboard "Layout Id"
for additional layouts with the same LANGID.

Signed-off-by: Derek Lesho <dlesho@codeweavers.com>

Signed-off-by: Derek Lesho <dlesho@codeweavers.com>

It is no longer used now that test_fpu_setup() uses create_device().

For the most part these were already sorted, but a few exceptions appear to
have crept in.