Disable broken vectorization tests on Windows and use windows-2022 in CI

[christiangnrd]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.84%. Comparing base (a1f79db) to head (6766d90).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #405   +/-   ##
=======================================
  Coverage   80.84%   80.84%           
=======================================
  Files          12       12           
  Lines         736      736           
=======================================
  Hits          595      595           
  Misses        141      141           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[christiangnrd]

@simeonschaub seems like #379 introduced windows test failures (other than #317) masked by the windows-2025 runners breaking

From worker 3:	ld.lld: error: undefined symbol: _cl_sin(float vector[2])
      From worker 3:	>>> referenced by C:/Users/runneradmin/AppData/Local\pocl/tempfile-70-50-fb-83-fa.o:(_pocl_kernel__Z6kernel13CLDeviceArrayI3VecILi2E7Float32ELi0ELi1EE3sinS2__workgroup)
      From worker 3:	error: linker command failed with exit code 1 (use -v to see invocation)

[simeonschaub]

Hmm, that's odd! I'd be fine with skipping these tests on windows for now, but would be good to figure out why pocl does not support explicit SIMD on these platforms.

[github-actions]

Your PR no longer requires formatting changes. Thank you for your contribution!

[christiangnrd]

Merging so CI can be useful again. I opened #415 to keep track of the workaround.