feat(botocore): add override service name to botocore integration

[quinna-h]

Motivation:

Currently traces in botocore derive their service name from the service and endpoint, ex. aws.s3 or aws.sqs, and there is no way to change the service name. Other integrations allow for changing the default service name either by setting environment variables, or configuring with config['service'] or config['service_name']. This PR adds support for these methods of overriding the service name, which allows individual traces to have custom service names.

Examples:

@mock_s3
ddtrace.config.botocore['service_name'] = "botocore" # this sets service name to botocore.s3
ddtrace.config.botocore['service'] = "boto-service" # this overrides previous and sets service name to boto-service.s3

export DD_BOTOCORE_SERVICE="boto" # this overrides previous settings and sets service & service name to boto.s3

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/add-c0f1d24cf11f23b7.yaml                            @DataDog/apm-python
ddtrace/contrib/botocore/patch.py                                       @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/botocore/services/bedrock.py                            @DataDog/ml-observability
ddtrace/contrib/botocore/services/kinesis.py                            @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/botocore/services/sqs.py                                @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/botocore/services/stepfunctions.py                      @DataDog/apm-core-python @DataDog/apm-idm-python
docs/configuration.rst                                                  @DataDog/apm-core-python
tests/contrib/botocore/test.py                                          @DataDog/apm-core-python @DataDog/apm-idm-python

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-07-18 21:24:11

Comparing candidate commit 11b474c in PR branch quinna/AIDM-210/botocore-service-naming with baseline commit ac1308b in branch main.

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

scenario:sethttpmeta-useragentvariant_exists_2

• 🟥 max_rss_usage [+1.435MB; +1.494MB] or [+7.032%; +7.321%]

scenario:sethttpmeta-useragentvariant_exists_3

• 🟥 max_rss_usage [+1.461MB; +1.525MB] or [+7.167%; +7.483%]

[datadog-datadog-prod-us1]

Library Vulnerabilities

    

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: quinna/AIDM-210/botocore-service-naming
Commit report: 97f31b5
Test service: dd-trace-py

✅ 0 Failed, 180 Passed, 783 Skipped, 7m 18.92s Total duration (23m 2.29s time saved)

[erikayasuda]

LGTM but I will leave the official approval to IDM and MLObs since these are their files

[erikayasuda]

@DataDog/ml-observability Could we get a review on this PR? 🙏 The automation didn't automatically tag someone from the team for some reason.