Right now, if TS has an error before we get back the full version string in the TSServer `'telemetry'` event, we end up logging just the basic version info (such as 3.8.0). We also want to include the pre-release tags (3.8.0-tsversion20200101)

For #88313

Also log updateGraph on `completions.execute` instead of as its own event

We are also exproting other values/types, so use a named export instead

Fixes #88313

For #87972

Fixes #86205

We already log error metadata for failed requests. However we don't include this on the fatalError event. This makes investigation of these errors difficult

Fixes #84826

For #85021

Splits `reset` from `reinitialize` and makes sure we always `resset` buffer sync support when the service starts

Some users are setting weird errors related to untitled TS files. In some of these cases (such as https://github.com/microsoft/TypeScript/issues/35091) we see a untitled file being sent to the tsserver without the `inMemoryResourcePrefix`.

I can't figure out how to get into this state but am removing the gating that *could* perhaps cause use not to set `inMemoryResourcePrefix`. This gating targets TS 2.7 or older, which telemetry shows very, very few users are still enabling in their workspaces

For #84185

Fixes #83338

`TextDocument` lifetime may not match that of the the user facing editors. However the JS/TS extension was assuming that it did. Introduce a `ensureHasBuffer` function that can open a buffer if vscode knows about a textdocument but no `onDidOpenTextDocument` has been fired for it yet

Telemetry shows that these old TS versions have very low usage (in the tens across the many, many js/ts users). Given this, it now makes sense to remove the extra gating/checks required to support these old versions

Workaround for TS not being able to handle interactive playground resource with query parameters in uri

Fixes #81059
Fixes #82419

The interactive playground generates uris that have query paramters. This causes the TS Server to crash. The workaround here is make sure the file paths we give to TS Server don't have query paramters but the ones we work with locally do

If one server fails for a command but the other does not, we are in an inconsistent state. Treat this as a fatal error

Any errors on `updateOpen` will cause the TS Server to become out of sync. This change alerts us to errors that happen in `updateOpen`. We then restart the ts server

We are interested in understanding which TS versions user have enabled in their workspaces, and how widely these diverge from these the workspace version

This is needed to help us better understand which TS versions users have enabled in their workspaces

Based on telemetry, these versions have pretty much zero usage in the past 30 days. Removing the extra gating code since we can now assume users are on TS > 2.2.

Fixes #75866

In most cases, were are only interested in the tsserver.log file, not the additional typings installer logs

Fixes #68896

For #64485

Batching file changes should be more efficent than sending requests one at a time.