feat(dsm): context support for sns

[michael-zhao459]

Added the proper support based on AWS message event format for sns -> lambda, as well as sns -> sqs -> lambda
This allows dsm to properly extract the neccessary context for lambda support

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-complete-sns-sqs-lambda-dsm-context-support-aa96ac74692ceb48.yaml  @DataDog/apm-python
ddtrace/internal/datastreams/botocore.py                                @DataDog/data-streams-monitoring
tests/datastreams/test_botocore.py                                      @DataDog/data-streams-monitoring

[github-actions]

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 287 ± 7 ms.

The average import time from base is: 288 ± 6 ms.

The import time difference between this PR and base is: -1.5 ± 0.3 ms.

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 1.894 ms (0.66%)

ddtrace.bootstrap.sitecustomize 1.243 ms (0.43%)

ddtrace.bootstrap.preload 1.243 ms (0.43%)

ddtrace.internal.remoteconfig.client 0.646 ms (0.23%)

ddtrace 0.651 ms (0.23%)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-06-05 14:23:49

Comparing candidate commit 9039d15 in PR branch michael.zhao/lambda-support with baseline commit 0e5abc9 in branch main.

Found 0 performance improvements and 4 performance regressions! Performance is the same for 549 metrics, 3 unstable metrics.

scenario:iastaspects-lstrip_aspect

• 🟥 execution_time [+1.340µs; +1.426µs] or [+10.278%; +10.944%]

scenario:iastaspects-rstrip_aspect

• 🟥 execution_time [+1.132µs; +1.419µs] or [+8.826%; +11.063%]

scenario:iastaspectsospath-ospathbasename_aspect

• 🟥 execution_time [+726.435ns; +843.968ns] or [+17.057%; +19.817%]

scenario:iastaspectsospath-ospathsplitext_aspect

• 🟥 execution_time [+552.984ns; +661.375ns] or [+12.194%; +14.584%]

[emmettbutler]

Is it actually valid to expect both this and line 185? Seems like they could be condensed into a single condition.

[michael-zhao459]

I can confirm that binaryValue is needed for sns -> sqs -> lambda but am worried about getting rid of the previous condition of BinaryValue, there are too many configurations that could result in the other state being accurate, if possible I would appreciate keeping both conditions