fix(ci): pin Windows runner to windows-2022 for SDK compatibility

[gtolontop]

Goal of this PR

Fix all Windows CI builds (FiveM, RedM, Server) failing with MSB8036: The Windows SDK version 10.0.22000.0 was not found since the windows-latest runner migrated to Windows Server 2025.

How is this PR achieving the goal

The windows-latest GitHub Actions runner label now resolves to Windows Server 2025, which does not include Windows SDK 10.0.22000.0 required by the build system (systemversion '10.0.22000.0' in code/premake5.lua).

This PR pins the Windows runner to windows-2022 which still includes the required SDK. This is a single-line change in ci_build.yml with zero impact on the build output.

Sources:

• GitHub: windows-latest migration to Windows Server 2025
• GitHub: Windows SDK missing on windows-latest
• GitHub: Add Windows 10/11 SDK request

This PR applies to the following area(s)

CI/CD build pipeline

Successfully tested on

• Verified that windows-2022 runner image includes Windows SDK 10.0.22000.0
• No changes to build configuration, toolchain, or output

Checklist

• Code compiles and has been tested successfully.
• Code explains itself well and/or is documented.
• My commit message explains what the changes do and what they are for.
• No extra compilation warnings are added by these changes.

Fixes issues

Fixes Windows CI builds failing on every PR since the windows-latest runner migration.

[gtolontop]

Why he don't want trigger the building test 😂

[gtolontop]

Figured it out lol this PR can't be CI-tested because:

pr_opened.yml file filter excludes .github/ paths and breaks the compilation check entirely
The workflow uses pull_request_target, so it always runs from master, not from the PR branch :(