Allow asterisks in comments

Once the parser passes a `/*` token, it proceeds to search for a `*/` token, throwing a SyntaxError as soon as it encounter an asterisk not immediately followed by a slash. Comments can contain asterisks though. Many of these comments in project files are autogenerated, for example based on a file name which could have an asterisk in it.

Could the parser ignore `*` characters between `/*` and `*/`, continuing its search without issue until it finds the closing `*/`?

To reproduce the below, call the parser on any (file containing a) line such as `/* Upload *.dSYM to Firebase */`:

```
Thrown:
{ [SyntaxError: Expected "*/" or [^*] but "*" found.
]
message: 'Expected "*/" or [^*] but "*" found.',
expected:
[ { type: 'class',
parts: [Array],
inverted: true,
ignoreCase: false },
{ type: 'literal', text: '*/', ignoreCase: false },
{ type: 'class',
parts: [Array],
inverted: true,
ignoreCase: false },
{ type: 'literal', text: '*/', ignoreCase: false } ],
found: '*',
location:
{ start: { offset: 697, line: 13, column: 35 },
end: { offset: 698, line: 13, column: 36 } },
name: 'SyntaxError' }
```

Individua il punto di ingresso del parser che gestisce i commenti /* e riproduci il problema con `/* Upload *.dSYM to Firebase */`. Traccia il modo in cui viene analizzato il corpo del commento, quindi verifica che un asterisco interno venga accettato mentre */ di chiusura continui a terminare il commento senza un SyntaxError.

Scritto dal modello di indicizzazione a partire dal testo della issue.