Handle the loop closing between ThreadsafeProxy's is_closed() check and dispatch

[zigpy-review-bot]

Closes #740. Follow-up to #727 and #739 — this closes out the last member of the RuntimeError: Event loop is closed teardown-race family.

ThreadsafeProxy.func_wrapper snapshots the loop object at construction, so #739's ordering fix (publish self.loop = None before closing) can't reach it: the worker thread can close the loop between the proxy's loop.is_closed() check and the dispatch via asyncio.run_coroutine_threadsafe() / loop.call_soon_threadsafe(), and both raise RuntimeError: Event loop is closed at the caller. This wraps both dispatches in try/except RuntimeError and treats close-during-dispatch exactly like already-closed: log the existing "Attempted to use a closed event loop" warning and drop the call. The except is narrow — both try blocks wrap only the scheduling call (for the async path, call() merely constructs the coroutine; its body never runs there), so no RuntimeError from user code can be swallowed.

Two review findings from pre-open review (details below) are folded in:

• Disconnected async proxy calls are now awaitable. The pre-existing is_closed() branch returned bare None for coroutine methods too, so real callers that await through a proxy (await self._gw.reset(), await self._gw.disconnect(), await self._gw.send_data(...)) got TypeError: object NoneType can't be used in 'await' expression when disconnected — trading one teardown exception for another. Both disconnected paths (already-closed and closed-mid-dispatch) now return an already-completed future for coroutine methods, so await proxy.method() resolves cleanly to None; sync calls still return None as before. On the race path the never-to-be-scheduled coroutine is explicitly closed, so it doesn't warn as never-awaited.
• EventLoopThread.run_coroutine_threadsafe() raises legibly when the loop is gone. After Clear EventLoopThread.loop before closing it #739 the shutdown-window failure there was AttributeError: 'NoneType' object has no attribute 'call_soon_threadsafe'; it now snapshots self.loop and raises RuntimeError("Event loop is not running"), closing the passed coroutine first so the failure path is warning-clean. The sole caller (uart.connect) already handles this via except Exception.

Tests

Four new tests. test_proxy_loop_closed_during_async_dispatch and test_proxy_loop_closed_during_sync_dispatch pin the race window by making loop.call_soon_threadsafe raise RuntimeError while is_closed() still returns False — a faithful stand-in, since a genuinely closed loop would trip the earlier guard. test_proxy_loop_closed_async pins the awaitable disconnected result on the already-closed branch, and test_thread_run_coroutine_threadsafe_loop_not_running pins the RuntimeError. All four fail on dev (two with the leaked RuntimeError, one with the TypeError, one with the AttributeError) and pass with the change.

Verification

• pytest tests/ → 445 passed (Python 3.14.5), also clean under -W error::RuntimeWarning (pins the no-leaked-coroutine behavior)
• With bellows/thread.py reverted to dev: the four new tests fail as described above, rest pass
• Pre-open review: an Opus subagent review (confirmed the except RuntimeError breadth is safe and flagged the coroutine leak on the raise path) and a Copilot CLI second opinion (GPT-5.6 Sol; flagged the await None TypeError) — both findings addressed as described
• pre-commit: autoflake, black, flake8, isort, codespell, ruff pass; pyupgrade/mypy fail on untouched files in the local hook env only (same Python 3.14 breakage as noted on Clear EventLoopThread.loop before closing it #739) — CI is the real check

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.55%. Comparing base (553ec35) to head (e7c1d94).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #741   +/-   ##
=======================================
  Coverage   99.55%   99.55%           
=======================================
  Files          64       64           
  Lines        4263     4281   +18     
=======================================
+ Hits         4244     4262   +18     
  Misses         19       19           

☔ View full report in Codecov by Harness.
📢 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.