fix(otel): align operation status spans

[zhongkechen]

Summary

• emit terminal durable.operation.status for completed CONTEXT spans
• omit durable.operation.status from STEP attempt spans while preserving durable.attempt.outcome
• apply the canonical semantics to both OTel plugins with success and failure coverage

Testing

• hatch run test:all (3078 passed, 2 skipped)
• hatch run types:check
• hatch fmt --check in the OTel package

Coordination

Aligns Python with the Java/JS status model tracked by aws/aws-durable-execution-conformance-tests#52 and the updated conformance requirements in aws/aws-durable-execution-conformance-tests#53.

[github-actions]

Codex AI review

• [P2] Preserve one-shot terminal hooks during replay — packages/aws-durable-execution-sdk-python/src/aws_durable_execution_sdk_python/operation/child.py:187: every ReplayChildren replay now emits another on_operation_end for an already-terminal context, contradicting the plugin contract and potentially double-counting metrics or side effects. Finalize replayed OTel spans through a replay-specific hook instead.

• [P2] Serialize synthetic end-hook delivery — packages/aws-durable-execution-sdk-python/src/aws_durable_execution_sdk_python/plugin.py:450: sync=True invokes plugins directly and concurrently from flat map/parallel branch threads. This breaks the prior callback threading contract and can race non-thread-safe plugins. Dispatch through the single plugin executor and wait for completion to preserve ordering.

• [P2] Derive context span outcome from terminal status — packages/aws-durable-execution-sdk-python-otel/src/aws_durable_execution_sdk_python_otel/execution_plugin.py:478, packages/aws-durable-execution-sdk-python-otel/src/aws_durable_execution_sdk_python_otel/invocation_plugin.py:571: context outcomes are now ignored entirely until on_operation_end, whose existing logic marks spans OK whenever error is absent. Because OperationEndInfo.error is optional, FAILED contexts without an error payload are exported as successful. Map span status from info.status and treat a missing failure payload as an unknown error.

Reviewed commit 4f5499654082855c06d78573662a34b27984b147. Workflow run

[SilanHe]

We'll have to port the span status changes in this PR to JS and Java:

Span	Python #604	JS (merged)	Java (#572)
Attempt span (STEP attempt)	success → OK, failure → ERROR + recordException (explicit OK on success)	failure → ERROR + recordException; success → UNSET (no OK)	failure → ERROR + recordException; success → UNSET (no OK)
Operation / CONTEXT span (at op end)	success → OK, failure → ERROR	failure → ERROR + recordException; success → UNSET	failure → ERROR + recordException; success → UNSET
Continuation span	OK / ERROR	ERROR only (UNSET on success)	ERROR only (UNSET on success)

[SilanHe]

I can get started on them once this is merged