Close the Redis pool in the documentation examples

[MaciejZet]

Summary

The Simple Usage example creates a Redis pool and returns. On redis 5.0 through 5.2, AbstractConnection.__del__ then calls _writer.close() after asyncio.run has closed the loop. The process prints RuntimeError: Event loop is closed and exits non-zero.

await redis.close() in a finally block disconnects those writers first. close() is the method Worker already uses, and it exists across redis>=4.2,<6. On redis 5 it forwards to aclose(). aclose() itself arrived in redis 5.0.1, so the examples stay runnable on redis 4.x.

The other documentation examples that call create_pool from asyncio.run close the pool the same way.

Fixes #480

Test plan

• redis 5.1.1 against a local Redis: leaving the pool open reproduces the traceback in the issue. docs/examples/main_demo.py, slow_job.py, and retry.py finish with no Event loop is closed.
• pytest tests/test_pool_shutdown.py (uses the existing testcontainers Redis fixture)

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

@@            Coverage Diff             @@
##             main     #533      +/-   ##
==========================================
- Coverage   96.27%   95.85%   -0.43%     
==========================================
  Files          11       11              
  Lines        1074     1085      +11     
  Branches      209      144      -65     
==========================================
+ Hits         1034     1040       +6     
- Misses         19       24       +5     
  Partials       21       21              

see 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5ee4b48...bedef79. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[MaciejZet]

The Python 3.14 / Redis 5 job hits the 10-second pytest timeout while the existing redis_container fixture is pulling redis:5. This causes 117 setup errors, including the added test, before its body runs. The other seven test jobs pass, including that test.

This matches the setup timeout reported in #529, with a CI fix proposed in #530. Could you rerun the failed job so we can check whether the test completes on Python 3.14?