Fix time.sleep double-counting on Python 3.13+

[hadizamani021]

Fixes #11

time.sleep() gained a native sys.audit event in Python 3.13, causing aiocop's wrapper to emit a duplicate event and inflate severity scores.

Changes

• Only patch time.sleep() on Python versions earlier than 3.13 (audit_patcher.py)
• Recognize time.sleep unconditionally in BLOCKING_EVENTS_DICT, regardless of whether the event originates from aiocop or the Python runtime (blocking_io.py)
• Updated documentation and docstrings that described time.sleep() as an example of a function without a native audit event
• Added tests verifying the exact number of emitted events (not just event detection) across Python 3.10–3.13

---

Note

Low Risk
Targeted version gate and explicit event registration with regression tests; no auth or data-path changes.

Overview
Fixes inflated severity when time.sleep runs on Python 3.13+, where the runtime already emits a native sys.audit event while aiocop’s patch wrapper was emitting a second one.

time.sleep is only monkey-patched on Python < 3.13 (audit_patcher.py). On 3.13+, detection relies on the built-in audit event instead of the wrapper.

time.sleep stays in BLOCKING_EVENTS_DICT on all versions (blocking_io.py), so sleep is still scored as heavy whether the event comes from the patch or from CPython.

Docs and tests were updated: version-specific patching behavior is documented, and regression tests assert a single time.sleep event per call and that get_patched_functions() only lists time.sleep below 3.13.

^{Reviewed by Cursor Bugbot for commit 75b7f3a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[adriaardila]

Hey! Just checked it and you are correct. Nice catch and thanks for the PR.