Fix block comment not recognized inside switch expressions

The NEWLINE handler's peek-ahead used skip_whitespace_and_comments,
which consumed block comments as skipped characters. When it decided
not to emit NEWLINE (e.g. because } follows the comment), the scanner
returned false and all advances rolled back. The internal tokenizer
then tokenized the leading / of /* as a standalone slash, leaving the
block comment unrecognized.

Fix: replace skip_whitespace_and_comments with skip_whitespace_and_line_comments
in the NEWLINE peek path. Block comments (/* */) are external tokens
and must not be consumed during peek — only line comments (//) are skipped.
When the peek now stops at /*, no continuation pattern matches, so NEWLINE
is emitted and the next scanner call correctly handles /* as BLOCK_COMMENT.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: aspeddro

grammar.js

@@ -253,7 +253,7 @@ module.exports = grammar({
         optional("export"),
         "type",
         optional("rec"),
-        sep1(seq(repeat($._newline), "and"), $.type_binding),
+        sep1("and", $.type_binding),
       ),
 
     type_binding: ($) =>
@@ -418,7 +418,7 @@ module.exports = grammar({
       seq(
         choice("export", "let"),
         optional("rec"),
-        sep1(seq(repeat($._newline), "and"), $.let_binding),
+        sep1("and", $.let_binding),
       ),
 
     let_binding: ($) =>