[Distributed] emit tracing from the thunk and from executeDistributedTarget
Wires the tracing entry points up on both sides of a distributed call.
On the caller side, the distributed thunk's remote branch gains an interval
around encoding the invocation -- spanning the 'record...' calls the thunk emits
through 'doneRecording' -- and an event just before 'remoteCall'. The encoding
statements are wrapped in a 'do'/'catch' that closes the interval with
'success: false' and rethrows, so a 'record...' call that throws cannot leave the
interval open. A 'defer' would be the natural way to write that, but the local
function a 'defer' lowers to mangles the same way as a 'defer' written in the
distributed function's own body, which produces duplicate symbols.
On the callee side, 'executeDistributedTarget' gains an interval around decoding
the invocation and another around executing the target, which splits inbound
handling into decode versus execute. Both are closed from a 'defer' so they
terminate on every path out of the function, including the several throwing ones.
Note that decoding the individual argument *values* happens inside the distributed
accessor via 'decodeNextArgument', so it falls in the execute interval rather than
the decode one.
The result handler event is emitted on both the returning and the throwing path,
reporting which one it was.