Add API-style methods `getScopeInformationAtPosition` & `getScopeRangeAtPosition`

[zm-cttae]

⚡️️ Feature Request

• [x] I'm using the latest version of vscode-textmate-languageservice available.
• [x] I searched existing issues, open & closed. Yes, my feature request is new.

Is your feature request related to a problem?

• As a: VS Code extension developer,
• I want to: get scope information for a specific Textmate grammar
• So that: I can consume token data within my extension in a performant manner - ⦿microsoft/vscode#99356

Describe the solution you'd like

• [x] ✨ Implement a static extension contribution registry that can fallback to vscode.extensions.all.
• [x] ✨ Add Textmate grammar resolver methods that can map contributions to their source extensions.

Tasks for the new maintainer @zm-cttae:

• [x] ✨ Wire the contribution registry to the TextmateLanguageService API constructor.
• [x] 🧪 Add automated tests for TypeScript token services from both browser & frontend.
• [x] Add getTokenInformationAtPosition method to main API for polyfill - vscode.TokenInformation.
• [x] Add getScopeInformationAtPosition method to get Textmate token data - TextmateToken.
• [x] Add getScopeRangeAtPosition method to get token range - vscode.Range.
• [x] Add simple function tests for the 3 API methods, and simple performance test.

NB: that we need to reverse sort data when computing active grammar or language definition.

Describe alternatives you've considered

Still rely on vscode.ExtensionContext but we want to make that optional!

[zm-cttae]

changed due date to May 01, 2023

[zm-cttae]

marked the checklist item ✨ Implement a static extension contribution registry that can fallback to vscode.extensions.all. as completed

[zm-cttae]

marked the checklist item ✨ Add Textmate grammar resolver methods that can map contributions to their source extensions. as completed

[zm-cttae]

marked the checklist item ✨ Wire the contribution registry to the TextmateLanguageService API constructor. as completed