Spurious failures of Web tests on Windows

[newpavlov]

Web tests spuriously fail on Windows on Run wasm-pack test --headless --chrome --features=js,test-in-browser with the following message:

 driver status: exit code: 1
driver stdout:
    Starting ChromeDriver 121.0.6167.184 (057a8ae7deb3374d0f1b04b36304d236f0136188-refs/branch-heads/6167@{#1818}) on port 50916
    Only local connections are allowed.
    Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.

Error: driver failed to bind port during startup
[2024-02-21T13:23:08Z ERROR tiny_http] Error accepting new client: A blocking operation was interrupted by a call to WSACancelBlockingCall. (os error 10004)

Similar errors also happen with Firefox and Edge.

[newpavlov]

As a workaround we have temporarily marked Web Windows tests as continue-on-error: true in #405.