feat(aws-sdk)!: SQS receive: use span links instead of processing spans

[seemk]

Which problem is this PR solving?

Drop SQS processing spans in favor of span links as per latest specification.

Fixes #707

Short description of the changes

Create a span link for each incoming message that has a propagation context.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.53%. Comparing base (8b09de9) to head (8c2c582).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2345      +/-   ##
==========================================
+ Coverage   89.52%   89.53%   +0.01%     
==========================================
  Files         192      192              
  Lines        9677     9679       +2     
  Branches     2009     2009              
==========================================
+ Hits         8663     8666       +3     
+ Misses       1014     1013       -1     

Files with missing lines	Coverage Δ
packages/instrumentation-aws-sdk/src/semconv.ts	100.00% <100.00%> (ø)
...ckages/instrumentation-aws-sdk/src/services/sqs.ts	100.00% <100.00%> (+1.51%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[seemk]

@jj22ee

[pichlermarc]

cc @jj22ee @trivikr (component owner)

[seemk]

@jj22ee @trivikr up to date

[dyladan]

@seemk the conflicts are because of a package naming restructure of the directory. Sorry for the excess work.

@jj22ee can you please take a look at this? This is now the specified behavior and I believe we should accept this change.

[seemk]

@seemk the conflicts are because of a package naming restructure of the directory. Sorry for the excess work.

@jj22ee can you please take a look at this? This is now the specified behavior and I believe we should accept this change.

@dyladan Updated

@jj22ee

[dyladan]

@jj22ee please give this a review. It is implementing spec behavior

[trentm]

^^ I merged with main (fixing a couple easy conflicts) so we can get the tests running here again.
I'd love to get this in.
I'll also add a ! to the title to mark this as a breaking change.

[trentm]

nit: There are enum value exports from the unstable semantic-conventions exports that could be used for 'receive' here (and aws_sqs above):

8674:export const MESSAGING_OPERATION_TYPE_VALUE_CREATE = "create" as const;
8685:export const MESSAGING_OPERATION_TYPE_VALUE_DELIVER = "deliver" as const;
8694:export const MESSAGING_OPERATION_TYPE_VALUE_PROCESS = "process" as const;
8705:export const MESSAGING_OPERATION_TYPE_VALUE_PUBLISH = "publish" as const;
8714:export const MESSAGING_OPERATION_TYPE_VALUE_RECEIVE = "receive" as const;
8723:export const MESSAGING_OPERATION_TYPE_VALUE_SEND = "send" as const;
8732:export const MESSAGING_OPERATION_TYPE_VALUE_SETTLE = "settle" as const;

However, this is very minor and could be done in a follow-up PR.