Give the lexer more tolerance while reading a CODE token

[dnbln]

I got tired of seeing something like this while editing action code:

simplescreenrecorder-2021-01-18_18.52.50.mp4

Might have been overkill to implement but it also fails if I put a (, [ or { inside a string literal and don't close it:

simplescreenrecorder-2021-01-18_19.11.23.mp4

So here are a few thoughts to improve it at least:

• Give it some idea of structural braces(see brace matcher)
• To some extent parse the rust code(worth looking at the pin and recoverWhile attributes in intellij-rust's rust grammar!)

[AzureMarker]

I was just noticing this again today, though mostly when adding a new nonterminal or modifying its grammar. Parsing fails when you have a partial definition (MyNonterminal: MyTyp^ or MyNonterminal: MyType = <name:^).

[dnbln]

In those cases the tokens are correct, just the parser doesn't know how to recover from them. With the CODE it's a different issue, where the lexer thinks the token ends at EOF or too soon (typed one )/]/} too many)