chore: add docs/ to apm-python code ownership [backport 2.10]

[erikayasuda]

Manual backport of #10041

• 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 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

(cherry picked from commit f64bd48)

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

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: backport-10041-to-2.10
Commit report: 207b021
Test service: dd-trace-py

✅ 0 Failed, 164342 Passed, 12332 Skipped, 10h 39m 30.69s Total duration (56m 58.98s time saved)
⌛ 3 Performance Regressions

⌛ Performance Regressions vs Default Branch (3)

• test_user_specified_service_integration_v1 - test_pymysql.py 3.31s (+2.69s, +431%) - Details
• test_schematized_unspecified_service_name_v0 - test_mako.py 3.05s (+2.45s, +406%) - Details
• test_collect_span_id - test_stack.py 6.76s (+5.75s, +572%) - Details

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-08-05 21:03:58

Comparing candidate commit 207b021 in PR branch backport-10041-to-2.10 with baseline commit a554900 in branch 2.10.

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