Fix Windows test execution and WebSocket cleanup

[minggangw]

• Run Windows setup and npm test as a single cmd command chain, propagating failures to the retry action.
• Prevent close() from hanging after failed WebSocket handshakes that emit no close event on Node 22.
• Clean up WebSocket links when close() races a pending connection attempt that fails.
• Add regression coverage for HTTP-derived and explicit WebSocket connections, idempotent cleanup, concurrent closure, and successful retries.

Fix: #1611

[Copilot]

🟢 Approval recommended

No blocking issues were identified.

Pull request overview

Updates the Windows workflow so setup and npm test run within the retry action.

Changes:

• Chains environment setup and tests in one cmd invocation.
• Uses call for batch setup and npm commands.

File summaries

File	Description
.github/workflows/windows-build-and-test.yml	Runs Windows setup and tests inside the retry action.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[coveralls]

coverage: 90.955% (-0.001%) from 90.956% — minggangw:fix-windows-workflow into RobotWebTools:develop

[Copilot]

🟡 Changes recommended

Concurrent closure during an in-flight failed handshake can still leave the underlying socket unclosed.

Get a fresh assessment by requesting another Copilot review.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Balanced