[win32] Fix initialization of thread dpi awareness

[akoch-yatta]

This commit moves the initialization of the thread DPI awareness into the creation method. It was done too late before which resulted in all calls do Display::messageProc being executed with the wrong DPI awarness if the thread dpi awareness differs from the process DPI awareness.

##How to test

1. Configure your execution javaw.exe to be started with system DPI awareness (https://www.eclipse.org/swt/faq.php#winexternalmanifestfile) :
   dpi1:dpiAwaretrue</dpi1:dpiAware>
   dpi2:dpiAwarenesssystem</dpi2:dpiAwareness>
2. Prepare a two monitor setup, e.g primary 100% and secondary 200%
3. Start the ControlExample with
   -Dswt.autoScale=quarter
   -Dswt.autoScale.updateOnRuntime=true
4. Move the example to the secondary monitor
5. Change the zoom of the primary monitor
   The shell will be layouted strange in some places,e.g. the right part in the ButtonTaB
   

[github-actions]

Test Results

   486 files  ±0     486 suites  ±0   7m 39s ⏱️ -21s
 4 159 tests ±0   4 151 ✅ ±0   8 💤 ±0  0 ❌ ±0 
16 390 runs  ±0  16 298 ✅ ±0  92 💤 ±0  0 ❌ ±0 

Results for commit 2ccae67. ± Comparison against base commit a4fe53b.

♻️ This comment has been updated with latest results.

[HeikoKlare]

Change looks sound and works as expected.