Refactors calls to languages.setLanguageConfiguration to declarative descriptions in language-configuration.json

[hediet]

This fixes #98621.

Edit from @alexdima: Since a couple of milestones, it is possible to express everything in the language configuration files, including the wordPattern and the onEnterRules. It is preferable to express the language configuration in JSON because this allows those features to work even when the main extension is not activated.

[aeschli]

As mentioned, I would remove the g from the wordPatterns in the language-configuration. Other than that. it all looks good!

[aeschli]

I believe the 'g' is mandatory for all word patterns. I has to do with the way we use the word pattern regexes.
So I would remove it from the language-configurations and always set it where we create the RegExp object.

So the extension can do "wordPattern": "(-?\\d..." * (unless i or u is needed as well)

[mjbvz]

Markdown changes look good. Should TypeScript also be updated?

vscode/extensions/typescript-language-features/src/languageFeatures/languageConfiguration.ts

Line 58 in d89e2e1

const jsxTagsLanguageConfiguration: vscode.LanguageConfiguration = {

[hediet]

Markdown changes look good. Should TypeScript also be updated?

vscode/extensions/typescript-language-features/src/languageFeatures/languageConfiguration.ts

Line 58 in d89e2e1

const jsxTagsLanguageConfiguration: vscode.LanguageConfiguration = {

I guess yes, but lets do that in another PR, otherwise this becomes a Frankenstein!
The typescript-basics language feature currently does not have separate language-configurations for ts and for tsx, however, the typescript-language-features registers different configurations for them.

Also, lets merge this after the May release so there is plenty of time to test these changes in the Insiders. I'm quite sure that my refactoring is correct, but it is very easy to screw up and copy the wrong thing.