[PATCH v3] user32/tests: Add more tests for GetMouseMovePointsEx.

[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=78590

Your paranoid android.


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

user32:
input.c:3221: Test failed: expected WM_NCHITTEST message
input.c:3222: Test failed: expected WM_RBUTTONDOWN message
input.c:3223: Test failed: expected WM_RBUTTONUP message
input.c:3252: Test failed: expected WM_LBUTTONDOWN message
input.c:3253: Test failed: expected WM_LBUTTONUP message
input.c:3306: Test failed: expected loop with WM_NCHITTEST messages
input.c:3359: Test failed: expected WM_LBUTTONDOWN message
input.c:3360: Test failed: expected WM_LBUTTONUP message

=== w10pro64_ar (32 bit report) ===

user32:
input.c:3221: Test failed: expected WM_NCHITTEST message
input.c:3222: Test failed: expected WM_RBUTTONDOWN message
input.c:3223: Test failed: expected WM_RBUTTONUP message
input.c:3252: Test failed: expected WM_LBUTTONDOWN message
input.c:3253: Test failed: expected WM_LBUTTONUP message
input.c:3306: Test failed: expected loop with WM_NCHITTEST messages
input.c:3359: Test failed: expected WM_LBUTTONDOWN message
input.c:3360: Test failed: expected WM_LBUTTONUP message