chore: update TypeScript to v5

[fisker]

No description provided.

[3cp]

I have seen weird ts v5.5 typing issue in other projects.
ts v5 seems trying to be too smart.

[fisker]

Maybe this solution is acceptable? microsoft/TypeScript#9998 (comment)

[3cp]

I think it's a ts bug, it assumes our nextToken(parser, ...) didn't mutate parser.token.
But parser.token = is right there in the implementation of nextToken.

[3cp]

I can reproduce the issue https://www.typescriptlang.org/play/?ts=5.5.3#code/JYOwLgpgTgZghgYwgAgCoQM5mQbwFDKHIwA2cA5gFzIAMyAPsgIwDceAvnnjAK4gJhgAexDIAtjzBxIACkhZq6LAEpcBIvLAA6UhWQBeZm054EIrMjiLM2QzmJkqtZOzZ5gMZDLg7HB-YY0qvhE4pLSEN7KbKEeXj665P6GTMHqoYRmIBhCJBBaJELkMgDkiSUANJa+FNHpLhx4QA

But the same typing error also pops up with ts v4.

The fix is ugly if ((a.flag as 0 | 1) === 1) {

[3cp]

Had a read of the ts github issue. It sounds like ts would not address this issue anytime soon.

If you have time to apply the parser.currentToken() or getToken() solution, please go ahead :-)

[3cp]

I am also very confused why we didn't have this issue with ts v4 and v3 before.

[fisker]

Done.