[win32] Refresh thread dpi awareness on hooks

[akoch-yatta]

This commit resets the DPI awareness for the WH_MSGFILTER hook, if called. For performance reasons that is only done, when runAsyncMessages will be triggered, as this can cause UI updates, which would be executed with the wrong DPI awareness context and cause UI glitches.

How to reproduce

Have monitor specific scaling active and at least two monitors.

1. Open an IDE opened on a primary monitor with a low zoom (e.g. 100%)
2. Open a Java File in the Editor
3. Move the IDE to a secondary monitor with a higher zoom (e.g. 200%)
4. Use the vertical scrollbar to scroll up and down and you should see an effect, e.g. on the LineNumberRuler

Bildschirmaufnahme.2025-02-10.121127.mp4

[github-actions]

Test Results

   502 files  ±0     502 suites  ±0   10m 23s ⏱️ + 2m 28s
 4 334 tests ±0   4 320 ✅ ±0   14 💤 ±0  0 ❌ ±0 
16 575 runs  ±0  16 466 ✅ ±0  109 💤 ±0  0 ❌ ±0 

Results for commit 918acf9. ± Comparison against base commit df1c412.

♻️ This comment has been updated with latest results.

[HeikoKlare]

What about extracting the whole set/reset logic into a separate method, so that this call looks something like this:

Suggested change

	long previousDPIAwareness = refreshDPIAwareness();
	if (runAsyncMessages (false)) wakeThread ();
	if (previousDPIAwareness > 0) {
	OS.SetThreadDpiAwarenessContext(previousDPIAwareness);
	}
	runWithProperDPIAwareness(() -> {
	if (runAsyncMessages(false)) wakeThread();
	});

and refreshDPIAwareness() is extended to runWithProperDPIAwareness(Runnable operation)

[akoch-yatta]

Adapted it accordingly

[HeikoKlare]

I think it would be nice to still execute the passed operation if isRescalingAtRuntime() == false, but just without correcting DPI awareness 😉

[HeikoKlare]

I know that preserving formatting should not be the primary goal when processing changes, but if so much code like here is affected where the history might be interesting for different reasons (e.g., to find the commit when this handling of the "bug in Windows" was introduced, I was wondering whether we could still achieve that here without reducing comprehensibility. For example, wrapping the whole block inside the if (!synchronizer.isMessagesEmpty()) { into a processMessages runnable or the like, which is then executed with proper DPI awareness inside that if block, i.e.:

if (code >= 0) {
   Runnable processMessages = () -> {
      // all the existing code
   }
   if (!synchronizer.isMessagesEmpty()) {
      runWithProperDPIAwareness(processMessages);
   }
}