github colorization doesn't handle pragmas

[StephenWeatherford]

(see https://review.docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/linter-rule-secure-secrets-in-params?branch=pr-en-us-206413#silencing-false-positives for example)

Repro:
```bicep
#disable-next-line secure-secrets-in-params // Doesn't contain a secret
param mypassword string
```
Currently rendered as:

#disable-next-line secure-secrets-in-params   // Doesn't contain a secret
param mypassword string

Expected: Something like:

@mumian Do you know if MS docs should be picking up bicep colorization? Most seems to be okay, but it has the #disable-next-line issue and also handles strings incorrectly (but github does handle string correctly):
Docs:

Github:

@description('SAS Token for accessing script path')

[anthony-c-martin]

@StephenWeatherford - MSDocs is using a very old fork of highlightjs, which I backported our grammar for: Duncanma/highlight.js#38 (original source of truth here: https://github.com/Azure/bicep/tree/main/src/highlightjs)

GitHub is using Lingust, which uses TextMate: github-linguist/linguist#5307 (source of truth here: https://github.com/Azure/bicep/tree/main/src/textmate)

We should also ensure we update our Monarch grammar when we add support for directives: https://github.com/Azure/bicep/tree/main/src/monarch

Here's the original issue I used to track support for various highlighting libraries (has some context): #596

[anthony-c-martin]

Well, after giving you all that context (I assumed I had a bug in my hljs implementation), I think hljs is doing tokenization correctly and MSDocs is just choosing to colorize a function as black (or white in night mode):

FYI, you can preview what our highlighting looks like by loading the baselines: https://htmlpreview.github.io/?https://raw.githubusercontent.com/Azure/bicep/main/src/highlightjs/test/baselines/basic.html

[StephenWeatherford]

@anthony-c-martin Thanks! To be more clear, though: The problem with github is the inappropriate highlighting of the keyword "in" in the middle of the #disable-next-line pragma, not any specific . This is an actual git code snippet:

#disable-next-line secure-secrets-in-params   // Doesn't contain a secret
param mypassword string = 'a string is in here for you'

For docs, likewise it's the inappropriate highlighting of the keyword "for" in a string (which is okay in github, see above).

Obviously not high priority, but did make me think maybe we don't have bicep-specific highlighting at all.

[anthony-c-martin]

Did some digging - looks like this was originally reported under #5127. I've fixed the issue with #5128, but my PR to backport to the MS Docs fork Duncanma/highlight.js#41 has not yet been merged.

@mumian - is this something you'd be able to follow up on internally by any chance?

[mumian]

I am working on this.

[mumian]

The response from the engineering team - we're in the process of transitioning to a new syntax highlighting system to align with visual studio code. We're not planning to make any updates to highlight.js right now.

See https://ceapex.visualstudio.com/Engineering/_workitems/edit/689006.