Add support for multiline comments.

[tacosontitan]

Multiline comments in JSON are defined in the same way they are in JavaScript:

Comment
    : Delimited_Comment
    ;
    
fragment Delimited_Comment
    : '/*' Delimited_Comment_Section* ASTERISK+ '/'
    ;
    
fragment Delimited_Comment_Section
    : SLASH
    | ASTERISK* Not_Slash_Or_Asterisk
    ;

fragment Not_Slash_Or_Asterisk
    : ~('/' | '*')    // Any except SLASH or ASTERISK
    ;

_{👆🏻 single-line comment lexical structure excluded.}

This issue requests the addition of support for multiline comments to the JSON library even though they aren't an official part of the spec. Many developers still add comments to JSON files and the JsonLexer could simply discard those, but that's likely a better decision for the consumer to make instead.

Acceptance Criteria

• JsonLexer returns CommentToken for multiline comments.
• Column number advances when horizontal movement is captured.
• Line number advances when vertical movement is captured.
  • Column number is reset to 0 when line number advances.
• Captured comments exclude leading/trailing whitespace.
  • 👆🏻 should be configurable.
  • 👆🏻 as a whole.
  • 👆🏻 per line.
• Test coverage for implementation.

[tacosontitan]

Related: #31