chore(di): don't redact env tokens from probe snapshots

[watson]

Summary of changes

Remove env from list of tokens to redact from Dynamic Instrumentation probe snapshots.

Depends on: DataDog/system-tests#3827

Reason for change

Feature parity

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/debugging/_redaction.py                                         @DataDog/debugger-python

[P403n1x87]

🙌 thanks!

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-01-15 15:27:31

Comparing candidate commit 9f1911c in PR branch watson/env-redaction with baseline commit fce6d75 in branch main.

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

[watson]

I've seen other PRs to this repo being merged with the changelog validation CI check failing. Is that ok in this case as well?