fix: node10 types and implementation resolution

[userquin]

Description

This PR includes the following fixes for node10 module resolution:

• add missing types
• fix wrong resolution and implementation in VP: @shikijs/vitepress-twoslash/cache-fs resolving to default package export (expand https://arethetypeswrong.github.io/?p=%40shikijs%2Fvitepress-twoslash%402.3.2 then expant entrypoints/node10 resolution and implementation and check the filename, check screenshots below)

/cc @antfu

About the *.mts typesVersions mapping in langs, langs-precompiled and theme packages, it is a hack to allow resolve both types and implementation correctly, I've send you a few DM at discord with some screenshots with the traces for both.

I also need to review a few repositories 😅

Linked Issues

Additional context

current cache-fs subpackage export

cache-fs subpackage export with this PR

[netlify]

❌ Deploy Preview for shiki-matsu failed.

Name	Link
🔨 Latest commit	6c3b65f
🔍 Latest deploy log	https://app.netlify.com/sites/shiki-matsu/deploys/67a6cc2509e4d70008ba4563

[netlify]

❌ Deploy Preview for shiki-next failed.

Name	Link
🔨 Latest commit	6c3b65f
🔍 Latest deploy log	https://app.netlify.com/sites/shiki-next/deploys/67a6cc2549bd410008244c00

[userquin]

I need to review why node10 resolving implementation to d.mts instead .mjs

[antfu]

Can we drop Node 10 already? 🤣

[userquin]

Can we drop Node 10 already? 🤣

Yeah, it is a pain... in fact your blog about Types for Submodules is wrong (@tmkx shared me), you shouldn't use the dts in typesVersions, the implementation resolution will resolve to the dts instead the implmentation (here to mjs files), you need to use .ts (if using compatible) or .mts (if using ESM only).