ci: use windows 2025 runners

[ShortDevelopment]

windows-2019 actions are unsupported as of 30.06.2025.

This PR updates the ci-config to run on the supported versions of the windows runner:

• windows-2022 → windows-2025
• windows-2019 → windows-2022

💥 Breaking changes

• The default CC configuration on windows used the WinGlob api.
  This config is broken on recent versions of Windows 11 as CC does not initialize WinRT using RoInitialize to allow for some optimizations.
• CC now uses the version of libICU that is shipped with Windows by default
  This removes compat of the default config with all windows versions < Version 1903 (May 2019 Update)
  Should be fine as Windows 10 is out-of-support anyway...

🧪 Tests

• Tests did assume win32 => WinGlob; that is obviously wrong now.
• Some baselines were WinGlob only => updated
• libICU did return incorrect values so two tests were disabled => fixed
  The "new" behavior is consistent with recent node.js and bun.js
  • Intl: platform.normalizeLanguageTag does not correctly handle valueless unicode extensions #4490
  • Intl: Investigate different behavior between engines on CanonicalizeLocaleList #2964

---

See actions/runner-images#12045
Fixes #7045
Fixes #4490

[rhuanjl]

So, the Windows globalisation implementation doesn't work on latest windows AND the ICU alternative fails too, weirdly the test runner seems to be crashing out after one of the fails rather than finishing and saying how many tests failed.... that is awkward.

A couple of test fails look like things that are may be fairly easily fixable e.g. ICU version mismatches to amend tests for or inconsistent conditions in the test suite that expect windows to not be ICU etc. Hopefully it's not overall too big a job but I have no setup I can work on this on.

[ShortDevelopment]

I'll look into this in the next view weeks

[rhuanjl]

The windows-2019 test runners are now disabled.... So all CI runs now fail.

[ShortDevelopment]

See History of changes to the ICU library in Windows.

[ShortDevelopment]

I'm not sure why these results changed...

[rhuanjl]

@ppenzin What do you think? This fixes INTL on windows newer than the May 2019 Update but breaks it on older versions - though the key change is just build config we could perhaps document how to build the older version?