Raise TimeoutError instead of queue.Empty in WebSocketSession

[Copilot]

WebSocketSession.receive() (and derived methods) leaked queue.Empty on timeout — an internal implementation detail. AsyncWebSocketSession already raises TimeoutError via anyio.fail_after(), so sync and async APIs were inconsistent.

Changes

• WebSocketSession.receive(): Catches queue.Empty from queue.Queue.get() and re-raises as TimeoutError
• Docstrings: Updated receive(), receive_text(), receive_bytes(), receive_json() to document TimeoutError instead of queue.Empty
• Tests: Added test_receive_timeout covering the new behaviour

Before / After

# Before
try:
    event = ws.receive(timeout=2.0)
except queue.Empty:  # implementation detail leaking through
    ...

# After
try:
    event = ws.receive(timeout=2.0)
except TimeoutError:  # consistent with AsyncWebSocketSession
    ...

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.51%. Comparing base (96dd777) to head (3241a91).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #139      +/-   ##
==========================================
- Coverage   99.83%   99.51%   -0.33%     
==========================================
  Files           5        5              
  Lines         612      615       +3     
==========================================
+ Hits          611      612       +1     
- Misses          1        3       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.