ci: use windows-2025

[mkniewallner]

https://github.blog/changelog/2024-12-19-windows-server-2025-is-now-in-public-preview/

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.0%. Comparing base (816a069) to head (b4deb3e).
Report is 1 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #978   +/-   ##
=====================================
  Coverage   93.0%   93.0%           
=====================================
  Files         37      37           
  Lines        994     994           
  Branches      98      98           
=====================================
  Hits         925     925           
  Misses        55      55           
  Partials      14      14           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mkniewallner]

Tests run faster with windows-2025:

• windows-2025:

Job	Run time
windows (3.9)	6m 18s
windows (3.10)	5m 52s
windows (3.11)	6m 29s
windows (3.12)	5m 3s
windows (3.13)	5m 13s
windows (pypy3.10)	8m 0s

• windows-2022:

Job	Run time
windows (3.9)	6m 47s
windows (3.10)	8m 21s
windows (3.11)	8m 50s
windows (3.12)	7m 10s
windows (3.13)	6m 41s
windows (pypy3.10)	9m 7s

But there is an error on the dry-run release job when building wheels for aarch64:

C:\hostedtoolcache\windows\Python\3.13.1\x64\libs\python3.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'ARM64'␍
D:\a\deptry\deptry\target\aarch64-pc-windows-msvc\release\deps\deptry.dll : fatal error LNK1120: 98 unresolved externals␍

This will need investigation.

[mkniewallner]

But there is an error on the dry-run release job when building wheels for aarch64:

C:\hostedtoolcache\windows\Python\3.13.1\x64\libs\python3.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'ARM64'␍
D:\a\deptry\deptry\target\aarch64-pc-windows-msvc\release\deps\deptry.dll : fatal error LNK1120: 98 unresolved externals␍

This will need investigation.

Actually, same issue happens with windows-2022, so probably not related, but let's hold off from merging this until we figure out what's going on.