fix(botocore): accept AWS ARN bedrock model IDs [backport 2.18]

[github-actions]

Backport e8d68ae from #11944 to 2.18.

This PR fixes the model ID parsing in the bedrock integration to additionally accept model IDs in AWS ARN format.

Previously bedrock only worked with base/foundation models which were of the format {model_provider}.{model_name}. However now bedrock has expanded to allow custom/provisioned/imported/prompt/inference/sagemaker models, following the typical AWS ARN format:

  Base model: "{model_provider}.{model_name}"
  Cross-region model: "{region}.{model_provider}.{model_name}"
  AWS ARNs: Prefixed by "arn:aws{+region?}:bedrock:{region}:{account-id}:"
        a. Foundation model: ARN prefix + "foundation-model/{region?}.{model_provider}.{model_name}"
        b. Custom model: ARN prefix + "custom-model/{model_provider}.{model_name}"
        c. Provisioned model: ARN prefix + "provisioned-model/{model-id}"
        d. Imported model: ARN prefix + "imported-module/{model-id}"
        e. Prompt management: ARN prefix + "prompt/{prompt-id}"
        f. Sagemaker: ARN prefix + "endpoint/{model-id}"
        g. Inference profile: ARN prefix + "{application-?}inference-profile/{model-id}"
        h. Default prompt router: ARN prefix + "default-prompt-router/{prompt-id}"

Currently if an AWS ARN gets submitted as the model ID (for example, prompt management or a provisioned model) then because we attempt to split the string into a 2/3-part period-separated list, our code breaks when there is no period delimitter in the string.

This PR makes a best effort attempt to check each case and extract a model provider and name from the model ID. However, due to the nature of some formats, we default model provider to "custom" and just return the model/prompt/resource ID from the rest of the AWS ARN.

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/fix-bedrock-model-id-parsing-611aea2ca2e00656.yaml   @DataDog/apm-python
tests/contrib/botocore/bedrock_cassettes/amazon_invoke_model_arn.yaml   @DataDog/ml-observability
tests/snapshots/tests.contrib.botocore.test_bedrock.test_invoke_model_using_aws_arn_model_id.json  @DataDog/apm-python
ddtrace/contrib/internal/botocore/services/bedrock.py                   @DataDog/ml-observability
docs/spelling_wordlist.txt                                              @DataDog/python-guild
tests/contrib/botocore/test_bedrock.py                                  @DataDog/ml-observability

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-01-15 21:25:48

Comparing candidate commit 4dad3e7 in PR branch backport-11944-to-2.18 with baseline commit 75a0205 in branch 2.18.

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

scenario:iast_aspects-ospathdirname_aspect

• 🟩 execution_time [-386.588ns; -317.001ns] or [-9.500%; -7.790%]

scenario:iast_aspects-ospathsplit_aspect

• 🟥 execution_time [+612.081ns; +672.375ns] or [+15.870%; +17.434%]