Fix color management issue on windows

[Dannny1]

This is just taken from git-db-usr@262b8a6
Since nobody has created PR from it before, i will just open one.

[Dannny1]

Ok, it's updated.

[TurboGit]

Almost there :) TIA.

[TurboGit]

@wpferguson : Would you be able to double check this on your Windows build before I merge? Nothing urgent as the merge windows for 5.6 will be open around Jan 19 at best.

[wpferguson]

@TurboGit I built and it works fine AFAIC see. I can't spin up a second monitor from my VM (maybe libvirt is too old, or I haven't found the correct instructions yet). I could throw the build out on pixls.us and ask for testers.

[TurboGit]

I could throw the build out on pixls.us and ask for testers.

Good idea yes. Thanks.

[Dannny1]

Before i created the PR i tested the original commit (on different system as i use linux).
It was able to get and use the profile. Even when profile was changed in OS during dt already running, after it was moved to different monitor it used correct profile. Entries from log on that computer:
_```
14.9156 [color profile] we got a new screen profile ROG XG279Q_d65_22-05-2023.icm' from the windows color profile api (size: 20412) 126.3981 [color profile] we got a new screen profile M16native_22-05-2023.icm' from the windows color profile api (size: 20552)
164.9649 [color profile] we got a new screen profile `ROG XG279Q_d65_22-05-2023.icm' from the windows color profile api (size: 20412)
256.3814 [color profile] we got a new screen profile `ROG XG279Q_user_p3_22-05-2023.icm' from the windows color profile api (size: 11984)
256.6663 [color profile] we got a new screen profile `M16native_22-05-2023.icm' from the windows color profile api (size: 20552)
258.4953 [color profile] we got a new screen profile `ROG XG279Q_user_p3_22-05-2023.icm' from the windows color profile api (size: 11984)

[TurboGit]

@Dannny1 : That's reassuring, but when a tricky feature like this is introduced and one that I cannot test myself (I'm not using Windows), I always ask for double checking.