emit per-call jsRpcCall spans and propagate stub origin for trace continuity

[apeacock1991]

Imported from #6750

Summary

Add per-call tracing for JavaScript RPC.

Changes

• Emit jsRpcCall spans on both caller and callee.
• Tag spans with the RPC method, operation, and target kind.
• Parent the callee onset to the call that opened the session.
• Add jsrpc.caller_span_id to correlate each callee dispatch with its caller.
• Preserve tracing relationships for pipelined calls, returned stubs/promises, and callbacks.
• Avoid retaining span state on untraced paths.

Testing

• Added streaming-tail tests for pipelined RPC calls.
• Added coverage for callback argument tracing.
• Updated existing tail-worker tracing expectations.

Screenshots

[ask-bonk]

APIError: Invalid Anthropic API Key

github run

[ask-bonk]

APIError: Invalid Anthropic API Key

github run

[ask-bonk]

APIError: Invalid Anthropic API Key

github run

[ask-bonk]

@apeacock1991 Bonk workflow failed. Check the logs for details.

View workflow run · To retry, trigger Bonk again.

[codspeed-hq]

Merging this PR will improve performance by 10.12%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 1 improved benchmark
✅ 71 untouched benchmarks
⏩ 129 skipped benchmarks¹

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
⚡	bm_Promise_Fib10	20.3 µs	18.5 µs	+10.12%

Tip

Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing apeacock/jsrpcTracing (477f106) with main (c15dd17)}

Footnotes

1. 129 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[apeacock1991]

Closing as rthe branch name didn't match internal