feat(language-service): Make MDX nodes typed with JSX.IntrinsicElements

[guyutongxue]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything or linked relevant results below
• I made sure the docs are up to date
• I included tests (or that’s not needed)

Description of changes

This PR tries to map MDX Markdown node to correct JSX node. The feature request is at https://github.com/orgs/mdx-js/discussions/2639 . Before, the MDX node are translated to <></> fragment in language service, which is not typed well (see microsoft/TypeScript#62358) and this PR changes them to a slightly corrected translation, such as <p></p>.

Benefit on this, we can do type-checking on JSX expression 'hole' inside Markdown contents, such as (e.g. translate to React JSX):

Also some open questions:

• The parser returns something like listItem { paragraph { innerContent } } for a compact list item, which is not the correct behavior according to CommonMark spec (says no <p> inside a
• if compact), so the original idea of typing <li> may not work;
• There are no source mappings of plain texts and tag names, so errors from those content's typing will be silenced;
• Documentation updates.

[changeset-bot]

🦋 Changeset detected

Latest commit: cc9043d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@mdx-js/language-service	Patch
@mdx-js/language-server	Patch
@mdx-js/typescript-plugin	Patch
vscode-mdx	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[remcohaszing]

The code looks great, but the tests need to be adjusted, notably the tests in https://github.com/mdx-js/mdx-analyzer/blob/main/packages/language-service/test/language-plugin.js.

[codecov]

Codecov Report

❌ Patch coverage is 96.49123% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 92.43%. Comparing base (5c96eac) to head (cc9043d).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/language-service/lib/virtual-code.js	96.49%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #515      +/-   ##
==========================================
+ Coverage   92.31%   92.43%   +0.11%     
==========================================
  Files          13       13              
  Lines        1927     1982      +55     
==========================================
+ Hits         1779     1832      +53     
- Misses        148      150       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[remcohaszing]

Ok this looks great! Just one small thing left: add a changeset, so we make a release.

1. From the repo root, run:

   npx changeset

2. Select all packages (We have to, because Changesets doesn’t fully understand VSCode extensions)
3. Mark all packages as being patch releases
4. Add a nice little one-liner summary

[remcohaszing]

Thank you! ♥️ This was just released. The MDX VSCode extension update can show up any moment now.