websocket: provide descriptive error on abnormal closure (fixes #4625)

[M-YasirGhaffar]

This relates to...

Fixes #4625

Rationale

When a WebSocket connection closes abnormally (code 1006) without completing the control frame exchange, the error event contained an empty TypeError message. This made debugging difficult as the error appeared cryptic with no description of what went wrong.

Changes

• Modified lib/web/websocket/websocket.js line 590 to use a fallback message when reason is empty
• Added test/websocket/issue-4625.js to verify the fix works for abnormal closures

Features

N/A

Bug Fixes

• When WebSocket closes without receiving a close frame (code 1006), the error message now provides a descriptive fallback: "WebSocket connection closed abnormally" instead of an empty string

Breaking Changes and Deprecations

N/A

Status

• I have read and agreed to the Developer's Certificate of Origin
• Tested
• Benchmarked (optional)
• Documented
• Review ready
• In review
• Merge ready

[KhafraDev]

Hard coding a fallback reason here goes against every other piece of code here. #4625 is not a bug either.