[Fix] Update AWS SDK Instrumentation to inject XRay trace context into HTTP Headers

[jj22ee]

• This is an alternative fix as opposed to [Fix] Update AWS SDK Instrumentation to inject XRay trace context into HTTP Headers #131

Issue #, if available:
Fixes the absence of broken X-Ray context propagation when the underlying HTTP instrumentation is suppressed or disabled.

Similarly to Java and Python, AWS SDK itself can inject the X-Ray Context into the HTTP Headers:

• Java example
• Python example
  
• See Specification that clarifies that AWS SDK instrumentations should use X-Ray propagator specifically.
  • https://github.com/open-telemetry/opentelemetry-specification/blob/v1.40.0/supplementary-guidelines/compatibility/aws.md?plain=1#L9-L12

Note - If the underlying HTTP instrumentation is enabled, then the underlying HTTP Child Span of the AWS SDK Span will overwrite the Trace Context to propagate through headers.

Description of changes:

• Move patched/extended instrumentations to an patches/extended-instrumentations/ directory
• Created AwsSdkInstrumentationExtended class that extends upstream AwsInstrumentation to add an additional instrumentation. The additional instrumentation will modify the HttpRequest class with an updated constructor to inject the X-Amzn-Trace-Id HTTP header.
  • Uses propwrap.ts that is taken from upstream OTel.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[mxiamxia]

I like the other option than this one. The other is more cohesive to the send method itself and middleware is the right tool to modify the request from my view. :)