OTel plugin produces disconnected X-Ray traces and groups retry attempts under wrong invocation

[ayushiahjolia]

The OTel plugin has three issues that degrade the X-Ray tracing experience:

1. When a step retries across invocations, both attempts appear under the second invocation because the operation spans share the same deterministic span ID.
2. Durable execution spans land in a separate X-Ray trace from the Lambda segments because System.getenv("_X_AMZN_TRACE_ID") returns stale values in Java Lambda runtimes.
3. Durable spans don't appear as a separate service node in the trace map (unlike the JS SDK), making them harder to identify in complex traces.