Add process spans to aws-1 sqs instrumentation

[laurit]

Aws-1 changes from #9778
This pr makes SQS instrumentation create similarly telemetry to kafka instrumentation, also support is added for the receive telemetry flag. Like in kafka instrumentation process span is created by placing messages in a custom list whose iterator creates span on next and closes it on hasNext.

[trask]

Like in kafka instrumentation process span is created by placing messages in a custom list whose iterator creates span on next and closes it on hasNext.

what do you think of making this opt-in with a warning? #1947 (comment)

[laurit]

what do you think of making this opt-in with a warning? #1947 (comment)

Making it opt-in is fine, but it raises the question what should the behavior be when this feature is disabled? Currently with default (receiver telemetry disabled) in this pr the only consumer side span is created is the process span from the iterator. If we allow disabling this process span should we create some other span, what should that be? Currently we create a receive span for each individual message, which probably doesn't conform to messaging semantic conventions.
The ability to link up producer span with spans created during message processing is a common request from our customers. While I totally agree that this instrumentation is flaky by design I don't remember any recent issues with kafka, so perhaps it is good enough to work in practice? Should we handle this in complaint driven way?

[trask]

I don't remember any recent issues with kafka

good point, maybe #5826 made things "good enough"

The ability to link up producer span with spans created during message processing is a common request from our customers.

ya, this is pretty important, you've convinced me, thx