[PATCH] user32/tests: Add more tests for GetKeyState from background thread.

[Marvin]

Hi,

While running your changed tests, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?

Full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=85133

Your paranoid android.


=== w10pro64 (32 bit report) ===

user32:
input.c:1292: Test failed: GetCursorPos: (99,100)

=== w10pro64_ja (64 bit report) ===

user32:
input.c:3268: Test failed: expected WM_NCHITTEST message
input.c:3269: Test failed: expected WM_RBUTTONDOWN message
input.c:3270: Test failed: expected WM_RBUTTONUP message
input.c:3299: Test failed: expected WM_LBUTTONDOWN message
input.c:3300: Test failed: expected WM_LBUTTONUP message
input.c:3353: Test failed: expected loop with WM_NCHITTEST messages
input.c:3406: Test failed: expected WM_LBUTTONDOWN message
input.c:3407: Test failed: expected WM_LBUTTONUP message
input.c:2747: Test failed: 0: expected WM_MOUSEMOVE message
input.c:2747: Test failed: 1: expected WM_MOUSEMOVE message
input.c:2747: Test failed: 2: expected WM_MOUSEMOVE message

=== w10pro64_zh_CN (64 bit report) ===

user32:
input.c:2747: Test failed: 0: expected WM_MOUSEMOVE message
input.c:2747: Test failed: 1: expected WM_MOUSEMOVE message
input.c:2747: Test failed: 2: expected WM_MOUSEMOVE message