chore: support python 3.13

[apiarian-datadog]

What does this PR do?

Adding Python 3.13 support.

Testing Guidelines

Unit tests, integration tests, and self-monitoring checks.

Motivation

SVLS-6020

Types of Changes

• Bug fix
• New feature
• Breaking change
• Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

• This PR's description is comprehensive
• This PR contains breaking changes that are documented in the description
• This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
• This PR impacts documentation, and it has been updated (or a ticket has been logged)
• This PR's changes are covered by the automated tests
• This PR collects user input/sensitive content into Datadog
• This PR passes the integration tests (ask a Datadog member to run the tests)

[apiarian-datadog]

This isn't ready since Python 3.13 isn't supported by the dd-trace-py yet.

[apiarian-datadog]

we kept hitting rate limit errors from dockerhub, so we're switching to the public aws ecr instead.

[apiarian-datadog]

the diff between the integration test snapshots for python 3.12 and 3.13 don't show any interesting differences, just notes that one of them is using python 3.12 and the other is using python 3.13.

[dbast]

dd-trace-py with Python 3.13 support got released some days ago, see https://github.com/DataDog/dd-trace-py/releases/tag/v2.19.0

[apiarian-datadog]

dd-trace-py with Python 3.13 support got released some days ago, see DataDog/dd-trace-py@v2.19.0 (release)

@dbast thanks for the reminder! i'll re-test our layer but since python 3.13 support in 2.19.0 is still somewhat experimental, we're planning to wait for the 2.20.0 release for actually releasing this change.

[christopherschroer]

dd-trace-py v2.20.0 was released

[apiarian-datadog]

no significant differences between the new python 3.13 integration test output files and their analogous python 3.12 versions

[duncanista]

Everything looks great, please make sure you create the equivalent changes necessary in self-monitoring so this runs on 3.13 on the core stacks: extension, fullinstrument, baseline, etc.