feat: config option to extract sqs context from message payload

[habmic]

Which problem is this PR solving?

• Context propagation between SNS to SQS didn't work without enabling AWS raw message delivery feature
• By default SNS message attributes are embedded within the payload when set to SQS

Short description of the changes

• Added a configuration (sqsExtractContextPropagationFromPayload ) that parse and extract the context propagation headers from the SQS payload ( off be default )

[blumamir]

LGTM

[codecov]

Codecov Report

Merging #737 (2bc3b2d) into main (82ebc49) will decrease coverage by 0.49%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #737      +/-   ##
==========================================
- Coverage   96.87%   96.37%   -0.50%     
==========================================
  Files          11       26      +15     
  Lines         640     1767    +1127     
  Branches      126      231     +105     
==========================================
+ Hits          620     1703    +1083     
- Misses         20       64      +44     

Impacted Files	Coverage Δ
...y-instrumentation-aws-sdk/src/services/dynamodb.ts	100.00% <0.00%> (ø)
...etry-instrumentation-aws-sdk/test/dynamodb.test.ts	100.00% <0.00%> (ø)
...ry-instrumentation-aws-sdk/test/aws-sdk-v3.test.ts	100.00% <0.00%> (ø)
...emetry-instrumentation-aws-sdk/src/services/sns.ts	93.33% <0.00%> (ø)
...opentelemetry-instrumentation-aws-sdk/src/utils.ts	97.29% <0.00%> (ø)
...etry-instrumentation-aws-sdk/test/testing-utils.ts	100.00% <0.00%> (ø)
...opentelemetry-instrumentation-aws-sdk/src/enums.ts	100.00% <0.00%> (ø)
...ry-instrumentation-aws-sdk/test/aws-sdk-v2.test.ts	100.00% <0.00%> (ø)
...ntation-aws-sdk/src/services/ServicesExtensions.ts	100.00% <0.00%> (ø)
...telemetry-instrumentation-aws-sdk/test/sns.test.ts	100.00% <0.00%> (ø)
... and 5 more

[blumamir]

Is anyone else planning to review this? if not I'll merge today

[Flarna]

Creating a spy on this scope effects all tests. You could move it into the relevant test/testsuite and instead of calling resetHistory() you could create a new spy for each test and use sinon.restore() after each test.

[Flarna]

Is this object structure documented somewhere? How should it look like for other propagators like e.g. Baggage or B3?

[Flarna]

Seems my review was too late :o) but there are anyway no blockers.

But I wonder that support for extract is added but not for inject.

[blumamir]

@Flarna Thanks for adding a review :)
@habmic - interested in implementing the above sinon refactor in a new PR?

[blumamir]

But I wonder that support for extract is added but not for inject.

Inject is always injecting the propagation headers into the message attributes at time of "Publish" \ "SendMessage"
When SNS forwards the message to SQS, it can place these headers as message metadata, or embed them into the payload. This is a configuration option for the SNS-SQS subscription.

This PR is about support for extracting the context for the second option - taking them from message payload, which is why only extract is relevant