Autocompletion of Template Literal Types with unresolved types.

**Extension**: Typescript Language Features
**Feature**: Autocompletion of Template Literal Types with unresolved types.

Hi,

Currently the autocompletion for template literal types stops working as soon as an ambiguous type is used in the template, like number or string.



My idea is, that instead of proposing nothing at all, the autocompletion feature can be extended to propose a snippet with a template literal string and tabstops for the parameters or alternatively a normal string. String unions could be replaced with choices. The end result after selecting the completion would look like something like that:


This could be for example helpful with APIs that typed their Ressource pathes using parametrized template literals.

Start with the TypeScript Language Features extension and reproduce the template-literal completion cases described in the report. Compare behavior for unresolved types, then clarify whether completion should produce a snippet with tab stops, a normal string, or union choices; done means the selected completion behaves consistently for these cases.

Written by the indexing model from the issue text.