chore(configurations): remove deprecated tracing env vars

[mabdinur]

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:

releasenotes/notes/remove-deprecated-tracing-configs-c6711b57037576f6.yaml  @DataDog/apm-python
ddtrace/settings/_config.py                                             @DataDog/apm-core-python
ddtrace/settings/_otel_remapper.py                                      @DataDog/apm-core-python
docs/configuration.rst                                                  @DataDog/python-guild
tests/appsec/iast/test_processor.py                                     @DataDog/asm-python
tests/integration/test_settings.py                                      @DataDog/apm-core-python
tests/internal/test_settings.py                                         @DataDog/apm-core-python
tests/opentelemetry/test_config.py                                      @DataDog/apm-sdk-api-python
tests/suitespec.yml                                                     @DataDog/python-guild @DataDog/apm-core-python
tests/telemetry/test_writer.py                                          @DataDog/apm-python
tests/tracer/test_encoders.py                                           @DataDog/apm-sdk-api-python
tests/tracer/test_sampler.py                                            @DataDog/apm-sdk-api-python

[mabdinur]

cc: @mtoffl01

Not sure if we should pull this out into it's own PR. DD_TRACE_128_BIT_TRACEID_LOGGING_ENABLED configuration is being removed so we need to enable this functionality by default.

Maybe this could use it's own release note.

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: munir/remove-deprecated-tracing-configs
Commit report: 81e0b95
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1468 Skipped, 5m 6.89s Total duration (35m 38.92s time saved)

[ZStriker19]

Similar to the changes above, should we log that analytics_enabled is not supported?

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-01-31 03:17:29

Comparing candidate commit 81e0b95 in PR branch munir/remove-deprecated-tracing-configs with baseline commit 0ed084a in branch 3.x-staging.

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