[Bug 53246] New: user32:sysparams - test_metrics_for_dpi() fails on Windows 10 1709+

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53246

Bug ID: 53246
           Summary: user32:sysparams - test_metrics_for_dpi() fails on
                    Windows 10 1709+
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: [e-mail]
          Reporter: [e-mail]

user32:sysparams - test_metrics_for_dpi() fails on Windows 10 1709+:

sysparams.c:4175: testing GetSystemMetrics with your current desktop settings
sysparams.c:3002: Test failed: 28: wrong value 136 vs 258
sysparams.c:3002: Test failed: 34: wrong value 136 vs 258
...
sysparams.c:2430: testing SPI_{GET,SET}DESKWALLPAPER
sysparams.c:3002: Test failed: 28: wrong value 136 vs 258
sysparams.c:3002: Test failed: 34: wrong value 136 vs 258

https://test.winehq.org/data/patterns.html#user32:sysparams

Where:
* 28 == SPI_SETMENUDROPALIGNMENT
* 34 == SPI_SETICONTITLELOGFONT

test_metrics_for_dpi() is actually called from multiple places and
unfortunately the traces make it hard to know which calls actually fail.

The first pair of failures probably come from:
     trace("testing GetSystemMetrics with your current desktop settings\n");
     test_GetSystemMetrics( );
     test_metrics_for_dpi( 192 );

The source of the second set of failures is less clear but presumably from the
other test_metrics_for_dpi( 192 ) call in test_dpi_aware(). Some
winetest_push_context() would be a good addition here.