chore(asyncpg): skip incompatible framework test

[mabdinur]

Description

The following tests asserts an asyncpg connection is garbage collected. This test is incompatible with the profiler and should be skipped: test_no_explicit_close_with_debug

Checklist

• Add additional sections for feat and fix pull requests.
• Library documentation and/or Datadog's documentation site is updated. Link to doc PR in description.

Motivation

Design

Testing strategy

Relevant issue(s)

Testing strategy

Reviewer Checklist

• Title is accurate.
• Description motivates each change.
• No unnecessary changes were introduced in this PR.
• Avoid breaking API changes unless absolutely necessary.
• Tests provided or description of manual testing performed is included in the code or PR.
• Release note has been added for fixes and features, or else changelog/no-changelog label added.
• All relevant GitHub issues are correctly linked.
• Backports are identified and tagged with Mergifyio.

[Kyle-Verhoog]

what change caused this? is this a new test in the asyncpg suite or a change we made to the profiler?

[mabdinur]

what change caused this? is this a new test in the asyncpg suite or a change we made to the profiler?

@jd do you know of any recent changes that would have caused this test to fail?

[Kyle-Verhoog]

@mabdinur how do we know it's profiling related?

[Kyle-Verhoog]

looks like there was a change in asyncpg but I haven't looked yet to see if it's flaky on their side too or if ddtrace is responsible.

[Kyle-Verhoog]

seems like it could be #4125 based on @Yun-Kim and I's findings. It lines up with the CI starting to flake too.

[Yun-Kim]

Failing framework test fixed by #4448.