feat(onboarding): early exit conditions in lib-injection [backport 2.10]

[github-actions]

Backport 0c38e09 from #9323 to 2.10.

This pull request adds "guardrails" to the "library injection" process. These are early exit conditions from the instrumentation process intended to avoid sending any traces when undefined behavior is likely. The code makes this determination on the basis of software versions present in the application environment, both of Python packages and the Python runtime itself.

The biggest risk here is that instrumentation is disabled when it's not intended to be. I think existing tests in tests/lib-injection cover this pretty well. There's a new test added that verifies instrumentation was cancelled when an unsupported package version is present.

Contains changes from #9418
Related RFC: "[RFC] One Step Guardrails"

Checklist

• minimum package version checks
• Testing
• replace envvars with inject_force
• figure out what to use instead of pkg_resources
• replace local file path with DD_TELEMETRY_FORWARDER_PATH
• Change(s) are motivated and described in the PR description
• Testing strategy is described if automated tests are not included in the PR
• Risks are described (performance impact, potential for breakage, maintainability)
• Change is maintainable (easy to change, telemetry, documentation)
• Library release note guidelines are followed or label changelog/no-changelog is set
• Documentation is included (in-code, generated user docs, public corp docs)
• Backport labels are set (if applicable)
• If this PR changes the public interface, I've notified @DataDog/apm-tees.

Reviewer Checklist

• Title is accurate
• All changes are related to the pull request's stated goal
• Description motivates each change
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Change is maintainable (easy to change, telemetry, documentation)
• Release note makes sense to a user of the library
• 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

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: backport-9323-to-2.10
Commit report: 34bdd36
Test service: dd-trace-py

✅ 0 Failed, 147399 Passed, 31488 Skipped, 9h 31m 55.96s Total duration (1h 57m 27.03s time saved)
❄️ 1 New Flaky

New Flaky Tests (1)

• test_accuracy - test_accuracy.py - Last Failure

  Expand for error

   Expected status 0, got 1.
   === Captured STDOUT ===
   === End of captured STDOUT ===
   === Captured STDERR ===
   Traceback (most recent call last):
     File "tests/profiling/test_accuracy.py", line 96, in <module>
       assert almost_equal(total_time(time_spent_ns, "spend_4"), 4e9)
   AssertionError
   === End of captured STDERR ===