Investigate differences in type checking of tsc vs tsserver requests

[typeholes]

As pointed out by microsoft/TypeScript#58337, type checking can proceed in different orders depending on whether it was triggered by a full tsc run or by a tsserver request like getting semantic info.

It would be interesting to trace the tsserver process but there are two obvious downsides:

1. tracing would add extra overhead when the editor experience is already laggy
   a. we can use a separate tsserver, like we do for the realtime metrics
2. the tracing code specifically disables recording types when in server mode
   a. this is moot, as we can just monkey path tracing.recordType