test(firewall): stabilize the peer storm release gate

[ClementG91]

Summary

• accept both IOException and TimeoutException for concurrent valid probes during the test's deliberate read-lane saturation
• preserve the actual product oracle: the listener must remain alive and serve a successful request after all hostile peers drain
• advance the release version to 0.11.3 rather than moving the already-pushed signed v0.11.2 tag

Root cause

The x64 release runner was more heavily scheduled than the PR/main runners. One valid probe consumed its client timeout while the test intentionally saturated the endpoint. The test comment already allowed scheduling timeouts, but its valid-worker catch handled only IOException. The listener remained healthy; the same tagged source passed Arm64 release and the packaged-service VM stress.

The v0.11.2 workflow published no GitHub release and no public assets.

Validation

• targeted peer-storm test: 10/10 consecutive passes
• full WinSight.Firewall.Tests: 158/158
• format verification and diff check: passed