feat: add support for python 3.12

[Yun-Kim]

Adds support for Python 3.12.

Checklist

• Change(s) are motivated and described in the PR description.
• Testing strategy is described if automated tests are not included in the PR.
• Risk is outlined (performance impact, potential for breakage, maintainability, etc).
• Change is maintainable (easy to change, telemetry, documentation).
• Library release note guidelines are followed. If no release note is required, add label changelog/no-changelog.
• Documentation is included (in-code, generated user docs, public corp docs).
• Backport labels are set (if applicable)

Reviewer Checklist

• Title is accurate.
• No unnecessary changes are introduced.
• Description motivates each change.
• Avoids breaking API changes unless absolutely necessary.
• Testing strategy adequately addresses listed risk(s).
• Change is maintainable (easy to change, telemetry, documentation).
• Release note makes sense to a user of the library.
• Reviewer has explicitly 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

[pr-commenter]

Benchmarks

Benchmark execution time: 2023-09-08 19:44:02

Comparing candidate commit 57317e6 in PR branch yunkim/add-py-312 with baseline commit b9c9efd in branch 2.x.

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

scenario:flasksimple-baseline

• 🟥 max_rss_usage [+765.509KB; +944.981KB] or [+2.300%; +2.840%]

scenario:flasksimple-debugger

• 🟥 max_rss_usage [+803.321KB; +932.564KB] or [+2.413%; +2.801%]

scenario:flasksimple-iast-get

• 🟥 max_rss_usage [+758.227KB; +906.387KB] or [+2.277%; +2.722%]

scenario:flasksimple-profiler

• 🟥 max_rss_usage [+758.903KB; +906.531KB] or [+2.278%; +2.721%]

scenario:flasksimple-tracer

• 🟥 execution_time [+306.933µs; +335.289µs] or [+5.151%; +5.627%]
• 🟥 max_rss_usage [+683.501KB; +859.462KB] or [+2.054%; +2.583%]

scenario:otelspan-start-finish

• 🟥 max_rss_usage [+758.492KB; +910.628KB] or [+2.648%; +3.179%]

scenario:sethttpmeta-collectipvariant_exists

• 🟥 max_rss_usage [+763.658KB; +926.761KB] or [+2.741%; +3.326%]

scenario:sethttpmeta-obfuscation-send-querystring-disabled

• 🟥 max_rss_usage [+1.044MB; +1.189MB] or [+3.752%; +4.273%]

scenario:sethttpmeta-obfuscation-worst-case-explicit-query

• 🟥 max_rss_usage [+833.141KB; +975.243KB] or [+2.972%; +3.478%]

scenario:sethttpmeta-obfuscation-worst-case-implicit-query

• 🟥 max_rss_usage [+1.033MB; +1.184MB] or [+3.711%; +4.252%]

scenario:sethttpmeta-useragentvariant_exists_1

• 🟥 max_rss_usage [+798.287KB; +949.067KB] or [+2.868%; +3.410%]

scenario:span-start-finish

• 🟥 max_rss_usage [+695.559KB; +866.246KB] or [+2.517%; +3.135%]

[P403n1x87]

I think we need to make sure we don't remove tests that are still relevant

[emmettbutler]

@ZStriker19 @P403n1x87 @majorgreys @shatzi @Kyle-Verhoog This is actually ready for review now, with all tests passing. Please approve again at your convenience!

[P403n1x87]

A couple of nits and questions. I think this needs a new rebase, otherwise LGTM!

[emmettbutler]

@P403n1x87 thanks for checking this out. what do you mean by "needs a new rebase"?

[P403n1x87]

@P403n1x87 thanks for checking this out. what do you mean by "needs a new rebase"?

Oh sorry, I should have said that the target branch probably needs a new rebase as I think some changes are also available in 1.x at the moment, but still show up as diff in this PR (e.g. ddtrace/debugging/_expressions.py should have no diffs now that #6835 is merged in 1.x)

[emmettbutler]

@P403n1x87 ah, thanks for clarifying. do you know of any reason that needs to happen before this gets merged?