'Unexpected token' check is breaking a bunch of Svelte tests

[Conduitry]

The 'Unexpected token' check added in #32 is introducing a lot of false positives or something, because hundreds of Svelte tests are failing now. I'm not sure why.

[Conduitry]

It looks like this is partially the result of using the x function in Svelte on things ending in a semicolon, which I guess is technically incorrect. Some failing tests are from something else though. Continuing to investigate whether this is something that should be addressed in Svelte of code-red.

[Conduitry]

All failing tests can be addressed by fixing how we're calling code-red throughout the Svelte compiler - by making sure we're using b instead of x where appropriate, by making sure we're not closing expressions in extraneous parentheses, and in a couple of places by removing stray }s. Closing.

[Conduitry]

Issues revealed by upgrade fixed in sveltejs/svelte#4385