Intellisense( suggestions ) stop working when encountering multi-line expression in parens with new-lines inbetween

### Imba Version: x.x.x

2.0.0-alpha.209

### Details

See title.

### Behavior

In the example below, ...

#### Expected

...intellisense continues to work as usual with any combination of empty and non-empty lines.

#### Actual

...stops working completely, instead.

### Your Environment

- Windows 10
- node.js 16.14.2

### Steps to Reproduce

1. Copy and paste the example below as is in VSC with the imba extension installed.
2. Notice that intellisense stops working by starting to add an inline event listener ( that is covered by the intellisense, i. e. click ) to any of the tag literals.
3. Try to arrange the lines as you wish ( adding more new-lines and removing any to see the effect ).
4. Notice that the only empty new-line that doesn't cause disruption is the one after the last non-empty one.
5. Notice that the imba-parser and ts-plugin remain unaffected.
6. Notice the loss of syntax highlighting for the tag name in the tag def below after you first tried to trigger the intellisense.

EDIT: Forgot to add code example. Will add it immediately.
EDIT: I could not reproduce a minimal for this after trying extensively. It only happened in this very specific setting that I can't post here as a minimal. It didn't even reproduce after I copy and pasted the content of the file as is in a new file in the same project, quite weird.

Start by reviewing the VS Code extension behavior described for multiline expressions in parentheses, using the reported Windows and Node.js environment if available. Compare the extension with the imba-parser and ts-plugin, which the report says remain unaffected. Done means the extension keeps IntelliSense and syntax highlighting working across empty and non-empty lines; a minimal reproduction is still needed.

Written by the indexing model from the issue text.