fix(eslint): Allow JSXNode to serialize

[genki]

Overview

Allow the JSXNode to serialize.

What is it?

• Feature / enhancement
• Bug
• Docs / tests / types / typos

Description

Even though there is the JSXNodeSerializer, the eslint has been warning when you use the JSXNode across the $ sign.
This PR solves this issue.

Use cases and why

Fixes #5864

Checklist:

• My code follows the developer guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• Added new tests to cover the fix / functionality

[netlify]

👷 Deploy request for qwik-insights pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	0ea5eb3

[wmertens]

Are you sure that this approach is enough? I would have thought that it needs changing here https://github.com/BuilderIO/qwik/pull/5883/files#diff-63ce4c4f15293afb89991dad20de59170680fe6145e0188174aea7365efed3b4R336

[genki]

@wmertens I am not sure, I couldn't come up with the issue.
I have tested for JSXNode, JSXOutput and ReturnType<typeof jsx> and got no warnings.
Are there something I have to think other than those types?
The JSXNode contains callable members, but the _isTypeCapturable function seemed to return true, if the type is once detected as an instance of JSXNodeImpl, without checking its inside.

[PatrickJS]

yeah I needed this

[gioboa]

Thanks @genki
We appreciate a lot your help 😎

[wmertens]

This will be available soon as the dev version on npm, please test.