Add tracing around os.Exec in node provider

[t0yv0]

Description

pulumi-language-nodejs starts node sub-processes to manage Pulumi projects. With these changes the subprocesses are now visible as spans in the Pulumi trace. The tagging convention is taken from pulumi-language-go. The change is small enough we might not need to highlight it in changelog.

Fixes # (issue)

Checklist

• I have added tests that prove my fix is effective or that my feature works

• I have updated the CHANGELOG-PENDING file with my change

• Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

[RobbieMcKinstry]

LGTM! Do you know if there's a way we can carry this trace forward in the node code? To get a fuller picture we should also instrument:

1. Running the Build script.
2. JIT compilation and interpretation
3. Labeling the trace with a tag indicating whether we're transpiling or not.

[RobbieMcKinstry]

Ah, also, I think this happens on the Go side, but we download and install dependencies too. I'm not sure if we have a trace for that or not. We will need pretty soon, I suspect, since that's likely to be another large speed up after transpilatino/slow booting. There are a number of issues around using Yarn 2 PnP instead of NPM to get a massive boost in download speed.

[t0yv0]

Yes! The https://opentelemetry.io/docs/instrumentation/js/getting-started/nodejs/#setup can be added to the node SDK and then Node can add traces too. We might need to migrate/upgrade opentracing to opentelemetry in the Go SDK first. This starts to sound like a large detour but given how difficult it seems to get an idea what Node is spending time on, maybe we should consider doing it?