ddraw/tests: Use todo_wine_if() in tests

[Marvin]

Hi,

While running your changed tests on Windows, 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=20563

Your paranoid android.


=== w1064 (32 bit ddraw4) ===
ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

=== w1064 (32 bit ddraw2) ===
ddraw2.c:2360: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

=== w1064 (32 bit ddraw1) ===
ddraw1.c:2209: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

=== w1064 (32 bit d3d) ===
d3d.c:2329: Test failed: Unexpected destination texture level pixels; 2031 differences at 0 level
d3d.c:2329: Test failed: Unexpected destination texture level pixels; 518 differences at 1 level
d3d.c:2329: Test failed: Unexpected destination texture level pixels; 138 differences at 2 level
d3d.c:2329: Test failed: Unexpected destination texture level pixels; 46 differences at 3 level
d3d.c:2513: Test failed: Unexpected destination texture level pixels; 257 differences
d3d.c:2660: Test failed: Unexpected destination texture level pixels; 256 differences at 2 level
d3d.c:2660: Test failed: Unexpected destination texture level pixels; 64 differences at 3 level
d3d.c:2660: Test failed: Unexpected destination texture level pixels; 16 differences at 4 level
d3d.c:2660: Test failed: Unexpected destination texture level pixels; 4 differences at 5 level

=== w1064 (32 bit ddraw7) ===
ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.