updated lexer to make the JSON-autodetect error reporting less confusing, particularly when the whole thing is dumped to JSON5 file: now the error report clearly identifies both the JSON5 parse error and JISON PARSER error that occurred: having both attempts fail (1 going through JSON5.parse, 2 going through a regular JISON plaintext input parse) results in such a report where we list both as the autodetect logic could not deliver and we need the user to decide which of these are "the most correct interpretation of the input". Note that we don't perform any heuristics as those get complicated pretty quickly and don't guarantee a correct decision when both paths result in a parse error: hence we simply report the error for both so the user can quickly see which is the more sensible error report of the two and then correct the input / disable the JSON input autodetect.
updated lexer to make the JSON-autodetect error reporting less confusing, particularly when the whole thing is dumped to JSON5 file: now the error report clearly identifies both the JSON5 parse error and JISON PARSER error that occurred: having both attempts fail (1 going through JSON5.parse, 2 going through a regular JISON plaintext input parse) results in such a report where we list both as the autodetect logic could not deliver and we need the user to decide which of these are "the most correct interpretation of the input". Note that we don't perform any heuristics as those get complicated pretty quickly and don't guarantee a correct decision when both paths result in a parse error: hence we simply report the error for both so the user can quickly see which is the more sensible error report of the two and then correct the input / disable the JSON input autodetect.

GerHobbelt/jison,GerHobbelt/jison,GerHobbelt/jison,GerHobbelt/jison