fix(otel): Fix span emission for cross-invocation operations and replay

[ayushiahjolia]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Issue Link, if available

#435

Description

Fixes OTel plugin span emission to correctly handle replay, cross-invocation operations, and virtual contexts.

Previously -

• Terminal operations replayed in subsequent invocations re-emitted spans with the same deterministic ID, causing X-Ray to overwrite invocation 1's spans
• Operations completing between invocations (wait, callback, invoke) had no continuation span showing they completed
• Suspended attempt spans ended with no status/outcome attribute
• Virtual contexts (map/parallel iterations) were invisible to the OTel plugin

Now -

• Skip onOperationStart for terminal replay operations (no more overwrites)
• Fire onOperationStart for non-terminal STEP/CONTEXT during replay (re-executed operations get a parent span)
• Create continuation spans with Links for operations that completed between invocations
• Mark suspended attempts as PENDING instead of bare end
• Emit spans for virtual contexts (aligned with other SDKs)

Checklist

• I have filled out every section of the PR template
• I have thoroughly tested this change

Testing

Unit Tests

Have unit tests been written for these changes? Yes

Integration Tests

Have integration tests been written for these changes? Yes

Examples

Has a new example been added for the change? (if applicable) Yes