feat(asyncpg): add capture_connection_cleanup option to silence pool cleanup spans

[RiyaChaturvedi37]

Closes #4264

Description

Adds a new capture_connection_cleanup option to AsyncPGInstrumentor
to allow silencing connection cleanup spans when using a pool.

When using a connection pool, asyncpg executes cleanup statements after
each invocation:

• SELECT pg_advisory_unlock_all()
• CLOSE ALL
• UNLISTEN *
• RESET ALL

These can pollute traces, especially for tasks that periodically query
the database. This option allows users to silence these spans.

Usage:

AsyncPGInstrumentor(capture_connection_cleanup=False).instrument()

The option defaults to True to maintain backward compatibility.

Type of change

• New feature (non-breaking change which adds functionality)

[tammy-baylis-swi]

Thank you for this @RiyaChaturvedi37 ! I have added some comments

[RiyaChaturvedi37]

Note: The large diff (+2440/-2389) is due to Windows line ending (CRLF) differences in the existing file on my local machine. The actual code changes are minimal — only 3 files with the new feature, tests, and changelog entry. I apologize for the noise!

[tammy-baylis-swi]

Thank you for fixes, lgtm! Just suggested a small docs update. The Maintainers will also have to review this.

[RiyaChaturvedi37]

Thank you for fixes, lgtm! Just suggested a small docs update. The Maintainers will also have to review this.

Done! Added the clarifying comment as suggested.

[github-actions]

This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment.
If you're still working on this, please add a comment or push new commits.