feat: migrate CI (win) to UCRT64 and use debug build for coverage

[FrogTheFrog]

Description

Migrate CI (win) to UCRT64 and use debug build for coverage

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.44%. Comparing base (d6c21b1) to head (7b808bb).

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
+ Coverage   76.01%   84.44%   +8.43%     
==========================================
  Files          11       10       -1     
  Lines         442      508      +66     
  Branches      250      282      +32     
==========================================
+ Hits          336      429      +93     
- Misses         37       44       +7     
+ Partials       69       35      -34     

Flag	Coverage Δ
Linux	84.37% <ø> (+5.65%)	⬆️
Windows	84.44% <ø> (+7.50%)	⬆️
macOS	51.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 9 files with indirect coverage changes