fix(scanner): Don't insert semicolon before constructor annotations

[punchagan]

No description provided.

[VladimirMakaev]

Thanks for the fix! I found two edge cases that the lookahead in check_annotation_then_constructor didn't handle and pushed a follow-up commit to your branch:

1. Fully-qualified annotations

class Foo
@com.example.Inject
constructor (x: Int) {}

The scanner read com as the annotation name and then saw ., which it didn't recognize as part of the annotation. It exited the annotation loop early, failed to find constructor, and incorrectly inserted ASI.

Fix: After reading word characters for the annotation name, also skip .-separated qualifier segments.

2. String literals containing parentheses in annotation arguments

class Foo
@Bar(name = "some ) text")
constructor (x: Int) {}

The ) inside the string literal decremented the parenthesis depth counter to 0, causing the scanner to exit the argument list prematurely. The same issue occurred with ( inside strings incrementing the counter.

Fix: When scanning inside (...), skip over "..." string literals (including \-escaped characters) without counting their contents as parentheses.

Both edge cases now have test coverage. All 289 tests pass.

[punchagan]

Thank you for the review, the improvements/fixes and the merge! 🎉 🙇