Run some checks on windows

[cptartur]

Closes #2716

Introduced changes

Checklist

• Linked relevant issue
• Updated relevant documentation
• Added relevant tests
• Performed self-review of the code
• Added changes to CHANGELOG.md

[ddoktorski]

I still think it would be better to test Windows only in the scheduled workflow. Testing it with every single change isn’t crucial and overall it will slow down our CI and make it harder to maintain.

[ddoktorski]

Can we create an issue to investigate whether the cache action functions correctly, considering that the first CI run on a branch takes significantly longer than subsequent runs, and on Windows it is much longer than on Linux?

Example:
https://github.com/foundry-rs/starknet-foundry/actions/runs/12178894598/job/33969862907 <- first run does not find any cache
https://github.com/foundry-rs/starknet-foundry/actions/runs/12179972960/job/33973292419

[cptartur]

Can we create an issue to investigate whether the cache action functions correctly, considering that the first CI run on a branch takes significantly longer than subsequent runs, and on Windows it is much longer than on Linux?

Example: https://github.com/foundry-rs/starknet-foundry/actions/runs/12178894598/job/33969862907 <- first run does not find any cache https://github.com/foundry-rs/starknet-foundry/actions/runs/12179972960/job/33973292419

@ddoktorski I'd just merge this and we'll see if te build times are problematic. And if so, we can disable these checks at any time.