OpenTelemetry Java Wrapper Layer doesnt connect to AWS lambda generated segment

[arun-annamalai]

Describe the bug
A clear and concise description of what the bug is.
[Java17 lambda runtime only] When I turn AWS lambda active tracing on, the span that is created the OpenTelemetry Java Wrapper Layer does not connect to the last span that the AWS lambda environment creates. I am invoking the lambda via console GUI. This indicates a problem with the context propagation from the lambda environment to the Java Wrapper Layer.

This bug does not reproduce in java11

Steps to reproduce
If possible, provide a recipe for reproducing the error.
Create a Java17 runtime lambda with java wrapper layer (arn:aws:lambda:us-west-2:184161586896:layer:opentelemetry-javawrapper-0_10_0:1)

What did you expect to see?
A clear and concise description of what you expected to see.
I expect to the span created by the java wrapper layer have the parent set to the span created by the lambda environment.

What did you see instead?
A clear and concise description of what you saw instead.
I saw that the span created by the java wrapper layer did not have a parent and was in a separate trace.

What version of collector/language SDK version did you use?
Version: (e.g., v0.58.0, v1.11.0, etc)
My lambda java application has the following otel sdk versions
opentelemetry-aws-xray-propagator-1.42.0-alpha
opentelemetry-api-1.42.1
opentelemetry-sdk-1.42.1
opentelemetry-aws-sdk-2.2-1.31.0-alpha

Lambda Env Variables
AWS_LAMBDA_EXEC_WRAPPER: /opt/otel-handler

Java: 17

What language layer did you use?
Config: (e.g., Java, Python, etc)
Java Wrapper Layer

Additional context
Add any other context about the problem here.

[tylerbenson]

You need to manually select the xray-lambda propagator instead of the xray propagator.