Reflecting changes in vscode to take ranges in SerializableSemanticTokensParams

[maryamariyan]

Reflecting changes in vscode-csharp after making ProvideSemanticTokensResponse take ranges as input.

• Modify SerializableSemanticTokensParams to take ranges rather than range
• Modify the data property of the SemanticTokensResponse class.
• Changes data to take an array of arrays of number type

Related to dotnet/razor#9092

Local testing:

• With feature flag disabled (default behavior for VS code), the ranges array contains one element as expected:
  

• With feature flag turned enabled, the ranges array contains sorted disjoined elements as expected:
  

Observation

• Realized that in vs code we are just using textmate, so the testing involved just assuring the values in ranges are properly mapped over, but the are not really used, in VS code we are just returning dummy empty responses for semantic range requests and just relying on text mate.

• Once we complete issue Enable CSharp Semantic tokens in VSCode razor#4323 we'd then be matching behaviors between VS and VS code.

[maryamariyan]

Noticing the Test OmniSharpt Test windows is failing on the CI but locally tests completed successfully for me:

Local output after running npm run test:

Test Suites: 1 passed, 1 total
Tests:       309 passed, 309 total
Snapshots:   309 passed, 309 total
Time:        14.113 s

I will rerun the CI to resolve the failures in the report, in case it happens to be intermittent.

[maryamariyan]

Seems like VS Code is not yet providing support for coloring certain strings and is causing the lines below to show up in red.

• This is not a regression. I tested this with 3 a week old vscode C# extension 2.0.376 and it still would reproduce with the colors below.

Based on this observation, I will be merging the pull request as it is.