PYTHON-5905 - Make logging tests not fail due to PyPy GC issues

[NoahStapp]

PYTHON-5905

Changes in this PR

PyPy's GC is non-deterministic, so cleanup commands from earlier tests can pollute the logs. Fixes this issue by filtering for the specific command and status we want before asserting.

Test Plan

Test changes.

Checklist

Checklist for Author

• [ ] Did you update the changelog (if necessary)?
• Is there test coverage?
• [ ] Is any followup work tracked in a JIRA ticket? If so, add link(s).

Checklist for Reviewer

• Does the title of the PR reference a JIRA Ticket?
• Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
• Is all relevant documentation (README or docstring) updated?

[Copilot]

Pull request overview

This PR updates the command-logging truncation tests to be resilient to extra structured command logs that can appear under PyPy due to non-deterministic garbage collection triggering cleanup commands during test execution.

Changes:

• Add a small helper (_get_command_log) to select the structured log entry matching a specific commandName and command status.
• Replace brittle cm.records[N] indexing with filtered lookups for STARTED/SUCCEEDED/FAILED command logs in both sync and async logger tests.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
test/test_logger.py	Uses a helper to locate the intended command log records before asserting truncation lengths (sync tests).
test/asynchronous/test_logger.py	Mirrors the same robustness improvements for async logger tests.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!