chore: introduce APM_TRACING RC product

[P403n1x87]

We introduce the APM_TRACING remote configuration product that allows dispatching remote configuration to the library for remote enablement/ configuration of library components and features.

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:

ddtrace/internal/remoteconfig/products/__init__.py                      @DataDog/remote-config @DataDog/apm-core-python
ddtrace/internal/remoteconfig/products/apm_tracing.py                   @DataDog/remote-config @DataDog/apm-core-python
ddtrace/debugging/_debugger.py                                          @DataDog/debugger-python
ddtrace/debugging/_products/dynamic_instrumentation.py                  @DataDog/debugger-python
pyproject.toml                                                          @DataDog/python-guild
tests/debugging/mocking.py                                              @DataDog/debugger-python
ddtrace/internal/remoteconfig/products/client.py                        @DataDog/remote-config @DataDog/apm-core-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: chore/apm-tracing-rc
Commit report: 7c4ca59
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1468 Skipped, 4m 50.35s Total duration (35m 10.03s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-02-19 15:49:34

Comparing candidate commit 3d93ec6 in PR branch chore/apm-tracing-rc with baseline commit 89689b8 in branch main.

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

scenario:iast_aspects-ospathbasename_aspect

• 🟥 execution_time [+326.159ns; +380.776ns] or [+9.754%; +11.387%]

scenario:iast_aspects-ospathsplit_aspect

• 🟥 execution_time [+408.004ns; +471.570ns] or [+10.585%; +12.235%]

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: chore/apm-tracing-rc
Commit report: 3d93ec6
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1184 Skipped, 1m 48.36s Total Time

[shatzi]

I think we should also record the right capabilities once they set.