Detect Notation Transformers dynamically

Clear and concise description of the problem

Currently, Shiki uses a single regex matcher for notation transformers. It resulted in a few problems:

Invalid syntax is included: JavaScript doesn't support # comment for adding comment, but notation transformers will still parse it as a normal comment.
Poor support of other formats: When using it with some formats, like the liquid template language, the current regex cannot match its comments.

Suggested solution

To solve the problem, we can use a specific matcher depending on the format/language, and allow people to customise it.

For example, when processing a JavaScript file, we only support JSX and JS style comments.

About the exact implementation, I think we can add a matchers map for different languages. When cannot find a matcher for current format, it fallbacks to our current regex matcher which supports common comment syntaxes.

const matchers = {
  javascript: [/regex1/, /regex2/],
  typescript: [/regex1/, /regex2/], 
  csharp: [/regex1/],
  ...
}

People can pass their own matchers object to customise it.

Alternative

For some notation transformers, we can use the corresponding meta transformer instead. like line/word highlight have their meta transformers, but this is not supported for all notation transformers.

Additional context

No response

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Contributes

[X] If this feature request is accepted, I am willing to submit a PR to fix this issue

shikijs / shiki