Fixed UDT syntax highlighting

[majastrz]

Fixed the recent regression in syntax highlighting for user defined types:

• Now emitting SemanticTokenType.Namespace for namespace symbols.
• Now emitting SemanticTokenType.Type for TypeVariableAccessSyntax that resolves to a valid type symbol.
• Now emitting SemanticTokenType.Keyword for null, true and false type keywords.

Examples of changes:

I will look into adding tests separately since we don't currently have baselines or meaningful unit tests for syntax highlighting. (I recall we had some issues with that in the past, but will need to confirm.)

This fixes #14147

Microsoft Reviewers: Open in CodeFlow

[github-actions]

Test this change out locally with the following install scripts (Action run 9590262619)

VSCode

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-vsix.sh) --run-id 9590262619

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-vsix.ps1) } -RunId 9590262619"

Azure CLI

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-cli.sh) --run-id 9590262619

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-cli.ps1) } -RunId 9590262619"

[jeskew]

Nice!

[github-actions]

Dotnet Test Results

    72 files   -     36      72 suites   - 36   23m 38s ⏱️ - 8m 42s
10 891 tests  -     20  10 890 ✅  -     20  1 💤 ±0  0 ❌ ±0 
25 678 runs   - 12 835  25 676 ✅  - 12 834  2 💤  - 1  0 ❌ ±0 

Results for commit 28c3da6. ± Comparison against base commit bf8a344.

[jeskew]

Will this end up highlighting an imported variable (accessed as a property on a wildcard import) as a type? E.g.,

mod.bicep

@export()
var foo = 'foo'

main.bicep

import * as mod from 'mod.bicep'

output foo string = mod.foo

[majastrz]

It highlights the mod part as a namespace but foo is highlighted as a variable: