feat: propagate trace-context for SQS and SNS in MessageAttributes

[trentm]

Propagate trace-context in SQS and SNS MessageAttributes, if there is
enough room (max 10 message attributes). Otherwise log.warn.
Spec: https://github.com/elastic/apm/blob/main/specs/agents/tracing-instrumentation-aws.md#distributed-tracing

Closes: #2021

Checklist

• tests
• SNS
• propagate even if hit transactionMaxSpans -> moved to investigate trace-context propagation after transaction_max_spans is hit #3109 as separate work
• changelog entry

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-01-19T19:22:19.298+0000

• Duration: 24 min 41 sec

Test stats 🧪

Test	Results
Failed	0
Passed	323202
Skipped	0
Total	323202

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run module tests for <modules> : Run TAV tests for one or more modules, where <modules> can be either a comma separated list of modules (e.g. memcached,redis) or the string literal ALL to test all modules

• run benchmark tests : Run the benchmark test only.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[trentm]

Some screenshots showing this working for SNS:

1. I have an "examples/trace-sns-publish.js" script that publishes a message to an SNS topic:

% node examples/trace-sns-publish.js us-west-2 trentm-play-topic1
SNS Publish to region=us-west-2 topicName=trentm-play-topic1
topicArn: arn:aws:sns:us-west-2:[REDACTED]:trentm-play-topic1
Publishing with message: "this is my message (0.1799853931829758)"
publish response data: {
  ResponseMetadata: { RequestId: 'a9de436a-d630-5515-9e0d-1f2940452da6' },
  MessageId: '5c48ac30-2d4d-5b23-a988-f073bb38f390'
}

2. That is received by an SNS trigger on a Lambda function of mine.

with the connection linked in the Span links tab of the Span details flyover: