fix: Windows CI

[liorr]

The main fix of the PR is updating the PowerShell web request command with a basic parsing option, as without it, the parsing would halt the job.

I've also added job-specific timeouts for Ubuntu and Windows runners to ensure that the jobs don't run indefinitely.

[Copilot]

Pull Request Overview

This PR aims to fix Windows CI issues by updating the workflow configuration. Key changes include:

• Adding job-specific timeouts for Ubuntu and Windows runners.
• Updating the PowerShell web request command with a timeout and basic parsing option.

Comments suppressed due to low confidence (3)

.github/workflows/ci.yaml:27

• Verify that a 3-minute timeout is sufficient for the Ubuntu job workload. If jobs tend to run longer, consider adjusting this value.

timeout-minutes: 3

.github/workflows/ci.yaml:97

• Ensure that a 6-minute timeout is appropriate for the Windows job, particularly under heavy CI load. Adjust if necessary to avoid premature job terminations.

timeout-minutes: 6

.github/workflows/ci.yaml:117

• Confirm that a 10-second timeout for Invoke-WebRequest is adequate for expected network latency. Additionally, review whether -UseBasicParsing is the best choice given the PowerShell version in use.

Invoke-WebRequest -Uri $env:TEST_URL -Verbose -TimeoutSec 10 -UseBasicParsing