chore(docs): remove DD_TRACE_ENABLED from configuration docs

[erikayasuda]

These are defined in the corporate docs, so we should just keep them there as the source of truth. The link to the corporate docs has also been added here.

See generated docs for this branch here

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:

docs/configuration.rst                                                  @DataDog/python-guild

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-12-19 19:28:46

Comparing candidate commit c1ae8ea in PR branch erikayasuda/remove-dd-trace-enabled with baseline commit 315a48f in branch main.

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