fix: event loop handler teardown bug

[jakelorocco]

Pull Request

Issue

Fixes N/A

Description

Cleans up the event loop handler teardown so that it doesn't log a warning when Python has already started tearing down module globals.

Testing

• Tests added to the respective file if code was changed
• New code has 100% coverage if code was added
• Ensure existing tests and github automation passes (a maintainer will kick off the github automation when the rest of the PR is populated)

Attribution

• AI coding assistants used

---

Adding a new component, requirement, sampling strategy, or tool?

If your PR adds or modifies one of the types below, check the matching box. A checklist of type-specific review items will be posted as a comment.

• Component
• Requirement
• Sampling Strategy
• Tool

NOTE: Please ensure you have an issue that has been acknowledged by a core contributor and routed you to open a pull request against this repository. Otherwise, please open an issue before continuing with this pull request.

[AngeloDanducci]

LGTM

[planetf1]

Looks good. I reproduced the __del__ warning on main (it needs something like a live daemon thread to keep the module around until shutdown wipes it) and it's gone with this change. One optional note on the test inline.

[planetf1]

Optional, fine to merge as is. Nothing here checks the "must not wait" part: I flipped the fallback to finalizing = False and this test still passed, because _event_loop is None holds either way. Wrapping handler._close_event_loop with mock.patch.object(..., wraps=...) and asserting it was called with join_timeout=0.0 would pin it. I checked that version fails on main and on the flipped fallback.