fix: Don't auto tag fragment if not in jsx

[akozlev]

Use treesitter to determine whether node is a jsx_opening_element and use this info to bail out if the user may be writing a generic parameter.

Solves issue mentioned in #202 (comment) where useState<> becomes useState<></> when the user is typing out a generic type argument in typescriptreact files.

A thing to note is that there is still an ambiguity in the grammar while typing:

// If the user types:
const foo = <T>

// It could be a generic function:
const foo = <T>() => { ... };

// Alternatively it could be a JSX element:
const foo = <T></T>;

But generic inline functions are less common than generic types and argument so this PR fixes most cases.

[PriceHiller]

Thanks for the PR 🙂!

The test failure is from an older issue that still needs to be fixed, not relevant to this PR.