Parent durable OTel spans to shared execution trace

[ayushiahjolia]

Issue #, if available: #674

Description of changes:

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

[github-actions]

Claude AI review

This PR reparents durable OTel spans (Workflow, Invocation, operations, attempts) onto one shared execution trace anchored to a propagated backend parent or a deterministic synthetic root, adds a DurableSampler/sampling-intent mechanism to resolve sampling once per invocation, and restructures context extractors to return a structured ExtractedContext. The trace-context resolution (canonical_trace_id, ExecutionTraceContext.resolve), sampling precedence, id namespacing (derive_execution_root_span_id), and the store_sampling_intent/DurableSampler wiring are internally consistent and well covered by the updated tests.

One correctness issue: both plugins now return early when execution_arn is missing without clearing _tracing_enabled, which _bind_sdk_tracer() set to True a few lines earlier. Because subsequent operation/user-function hooks only gate on _tracing_enabled, this leaves the plugin in a half-enabled state for the rest of the invocation, contradicting the "telemetry is disabled for this invocation" intent. See the two inline comments:

• packages/aws-durable-execution-sdk-python-otel/src/aws_durable_execution_sdk_python_otel/invocation_plugin.py:463
• packages/aws-durable-execution-sdk-python-otel/src/aws_durable_execution_sdk_python_otel/execution_plugin.py:340

Residual test risk: the new test_invocation_start_without_execution_arn_disables_tracing tests (in both plugins) only drive on_invocation_start/on_invocation_end, so they don't exercise the operation hooks and don't catch the stale-_tracing_enabled behavior. Adding a case that fires on_operation_start/on_user_function_start after a no-ARN start would guard this path.

Reviewed commit 9ff9f5561b298221fbb08b9620043fb7a2cbb7a7. Workflow run

[github-actions]

Codex AI review

[P1] Preserve the existing ContextExtractor contract. This exported API previously returned an OpenTelemetry Context; _ensure_extracted_context now rejects every existing custom extractor, causing telemetry to be disabled after the plugin executor swallows the TypeError. Accept and adapt legacy Context results, including their trace state and sampling flags, while introducing ExtractedContext through a compatible migration path and test that behavior.

[github-actions]

Codex AI review

[P1] This assertion fails for the parameterized ExecutionOtelPlugin. That plugin deliberately drops unfinished operation spans on a PENDING invocation, so only the resumed wait span is exported and len(waits) is 1; two spans are produced only by InvocationOtelPlugin. Split the expected count by plugin type, or change the execution-view lifecycle if exporting suspended segments is intended.

[github-actions]

Codex AI review

Found two blocking issues: a public context-extractor compatibility regression and a failing parameterized end-to-end assertion.

Reviewed commit e6f3f01211a81dd7a993421188ee7ddacd081225. Workflow run