[Bug] Typescript does not use the same trigger characters as VS Code

[schiem]

Reproducible in vscode.dev or in VS Code Desktop?

• Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

• Not reproducible in the monaco editor playground

Monaco Editor Playground Code

monaco.editor.create(document.getElementById('container'), {
	value: "type Foo = 'foo' | 'bar';\nconst doSomething = (foo: Foo): void => {\n    // Do something\n}\ndoSomething('')",
	language: 'typescript'
});

Reproduction Steps

1. Create a type in Monaco that consists of string literals
2. Create a function which uses that type as a parameter
3. Attempt to call that function

Actual (Problematic) Behavior

Autocomplete does not appear until you manually bring it up with ctrl + space, both after typing the opening parenthesis and the opening quote.

Expected Behavior

Autocomplete (with options 'foo' and 'bar', in the case of the example) appears as soon as you type a quote in the function parameter. This is how it VS Code works, both in the desktop and the browser.

Additional Context

This seems to be caused by the different triggers characters in the SuggestAdapter, in Monaco and in VS Code. It's possible that this is intentional behavior, but I couldn't find it documented anywhere.

This issue was brought up in #2883, but was not marked as a bug there.

[jacks-bush]

I would also like this to be added