feat: add Python 3.11 support to Dynamic Instrumentation

[P403n1x87]

Description

This change adds Python 3.11 support to Dynamic Instrumentation by adapting the bytecode required for injecting hooks and wrapping functions at the bytecode level. It also adapts the compiler of the DI expression language for conditional probes and expressions.

Checklist

• Followed the library release note guidelines when writing a release note.
• 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

Python 3.11 has been released and support for it has been added in the bytecode dependency. This means that we can now add Python 3.11 support to every part of the library that directly depend on features exposed by said dependency.

Design

Python 3.11 support required consistent adaptation in the opcodes used to perform injection and wrapping. Most notably are the no-op instructions for specialisation and the new exception table for zero-cost exception handling.

Testing strategy

The existing test suite should already have enough test cases to provide a comprehensive coverage to ensure that all the necessary features have been adapted as necessary.

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 and follows the library release note guidelines, or else changelog/no-changelog label added.
• All relevant GitHub issues are correctly linked.
• Backports are identified and tagged with Mergifyio.

[Yun-Kim]

LGTM other than one small release note fix 🥳

[codecov-commenter]

Codecov Report

Merging #4854 (c7bab68) into 1.x (a6ff0c3) will decrease coverage by 0.10%.
The diff coverage is 24.85%.

@@            Coverage Diff             @@
##              1.x    #4854      +/-   ##
==========================================
- Coverage   74.95%   74.85%   -0.10%     
==========================================
  Files         824      824              
  Lines       63924    64043     +119     
==========================================
+ Hits        47914    47942      +28     
- Misses      16010    16101      +91     

Impacted Files	Coverage Δ
ddtrace/debugging/_debugger.py	85.67% <ø> (+0.65%)	⬆️
tests/internal/py35/test_wrapping.py	0.00% <ø> (ø)
tests/internal/py36/test_wrapping.py	0.00% <0.00%> (ø)
tests/internal/test_injection.py	0.00% <0.00%> (ø)
tests/internal/test_wrapping.py	0.00% <0.00%> (ø)
ddtrace/internal/wrapping.py	75.81% <42.55%> (-1.05%)	⬇️
ddtrace/debugging/_expressions.py	79.88% <100.00%> (+0.22%)	⬆️
ddtrace/internal/injection.py	77.14% <100.00%> (+2.14%)	⬆️
ddtrace/internal/utils/inspection.py	100.00% <100.00%> (ø)
tests/debugging/test_expressions.py	100.00% <100.00%> (ø)
... and 2 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[brettlangdon]

@mabdinur since this modifies the bytecode wrapping code that we use for GraphQL is there any additional testing/concerns we should check/test for this?

That seems to be the "major" impact this change would have cross-product. Otherwise, most changes are isolated to DI.

[mabdinur]

@mabdinur since this modifies the bytecode wrapping code that we use for GraphQL is there any additional testing/concerns we should check/test for this?

That seems to be the "major" impact this change would have cross-product. Otherwise, most changes are isolated to DI.

We'll need to update our riot configurations to run graphql and graphene tests with py3.11:

dd-trace-py/riotfile.py

Line 1803 in 8a9fec4

name="graphql",

. If those tests pass we should be good. I'll add that as a follow up PR

[brettlangdon]

@mabdinur since this modifies the bytecode wrapping code that we use for GraphQL is there any additional testing/concerns we should check/test for this?
That seems to be the "major" impact this change would have cross-product. Otherwise, most changes are isolated to DI.

We'll need to update our riot configurations to run graphql and graphene tests with py3.11:

dd-trace-py/riotfile.py

Line 1803 in 8a9fec4

name="graphql",

. If those tests pass we should be good. I'll add that as a follow up PR

Is there any manual testing Gab (or you) could do to confirm this PR is ok to merge?

I'd hate to merge this code, then find out it messed up GraphQL wrapping code after.

[mabdinur]

I ran graphql-core and graphene tests with py3.11 and the changes in this branch, and most of the tests passed ( uses an itertable that was removed in py3.11). The failing tests were due graphql-core<2.3 using a deprecated type.

I think we should be good to merge this change.