fix(pymongo): use bytecode wrapping to trace pymongo clients

[mabdinur]

Resolves: #10344

• Uses bytecode wrapping instead of wrapt's objectproxys to instrument mongo clients and socket connections
• Previously the pin object used in the MongoClient was different from the ones used to trace socket connections. Updates usages of the Pin object to ensure sever, socket, and client objects use the same Pin. This sublte fix required updating the span counts in tests (now the DummyTracer used in tests is expected to capture one more span per trace).
• Updates the mongoengine integration to simply use the pymongo integration. This integration no longer does anything special and can be removed.
• Improves the test coverage of the pymongo integration. Ensures every pymongo version range with custom patching has test coverage.

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

.riot/requirements/12616cb.txt                                          @DataDog/apm-python
.riot/requirements/14b37e6.txt                                          @DataDog/apm-python
.riot/requirements/167d6de.txt                                          @DataDog/apm-python
.riot/requirements/1fd0884.txt                                          @DataDog/apm-python
.riot/requirements/3343686.txt                                          @DataDog/apm-python
.riot/requirements/d66afaf.txt                                          @DataDog/apm-python
releasenotes/notes/munir-pymongo-fix-patching-545f3947644c91cd.yaml     @DataDog/apm-python
ddtrace/contrib/internal/mongoengine/patch.py                           @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/internal/mongoengine/trace.py                           @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/internal/pymongo/client.py                              @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/internal/pymongo/patch.py                               @DataDog/apm-core-python @DataDog/apm-idm-python
riotfile.py                                                             @DataDog/apm-python
tests/contrib/mongoengine/test.py                                       @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/pymongo/test.py                                           @DataDog/apm-core-python @DataDog/apm-idm-python

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-09-09 22:55:43

Comparing candidate commit 139ec05 in PR branch munir/pymongo-fix-patching with baseline commit bdeb1ad in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 354 metrics, 46 unstable metrics.

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: munir/pymongo-fix-patching
Commit report: 139ec05
Test service: dd-trace-py

✅ 0 Failed, 8026 Passed, 2046 Skipped, 1h 37m 56.07s Total duration (34m 25.39s time saved)

[erikayasuda]

Just a few questions for my own clarification. LGTM!