Stabilize long-sleep-not-forever (ASYNC116)

[ntBre]

Tests and docs look good

[github-actions]

ruff-ecosystem results

Linter (stable)

ℹ️ ecosystem check detected linter changes. (+0 -4 violations, +0 -0 fixes in 1 projects; 54 projects unchanged)

python-trio/trio (+0 -4 violations, +0 -0 fixes)

- src/trio/_core/_tests/test_mock_clock.py:115:26: RUF100 [*] Unused `noqa` directive (non-enabled: `ASYNC116`)
- src/trio/_core/_tests/test_mock_clock.py:97:26: RUF100 [*] Unused `noqa` directive (non-enabled: `ASYNC116`)
- src/trio/_tests/test_ssl.py:717:39: RUF100 [*] Unused `noqa` directive (non-enabled: `ASYNC116`)
- src/trio/_tests/test_ssl.py:742:39: RUF100 [*] Unused `noqa` directive (non-enabled: `ASYNC116`)

Changes by rule (1 rules affected)

code	total	+ violation	- violation	+ fix	- fix
RUF100	4	0	4	0	0

Linter (preview)

✅ ecosystem check detected no linter changes.

[ntBre]

The ecosystem changes are previously-unused noqa codes for ASYNC116 that are now used on stable. I took a look at these to see where a real project needed to use a noqa for this rule, but it was just trio intentionally testing long sleeps, with comments to support that:

    # ignore ASYNC116, not sleep_forever, trying to test a large but finite sleep
    await sleep(100000)  # noqa: ASYNC116