PYTHON-5821 - Fix ordering issue between event publish and logging fo…

[NoahStapp]

…r connection creation and ready

PYTHON-5821

Changes in this PR

Follow-up to #2796 that fixes the same issue for connection creation and ready events/logs.

Test Plan

Existing tests.

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 addresses a race/ordering issue between CMAP event publication and connection-related debug logging by ensuring the debug log is emitted before publishing the corresponding CMAP events for connection creation and connection ready. This is a follow-up to #2796, extending the same ordering guarantee to additional connection lifecycle points.

Changes:

• Reordered connection_created emission to occur after the corresponding CONN_CREATED debug log.
• Reordered connection_ready emission to occur after the corresponding CONN_READY debug log.

Reviewed changes

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

File	Description
pymongo/synchronous/pool.py	Reorders connection created/ready CMAP event publication to occur after debug logging.
pymongo/asynchronous/pool.py	Reorders connection created/ready CMAP event publication to occur after debug logging (async pool).

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!