feat(vite): use externality to resolve externals for ssr dev bundler

[danielroe]

🔗 Linked issue

some context: nuxt/nuxt#11824
closes nuxt/nuxt#12219

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR replaces the current externals check with one based on wp5's resolution algorithm using externality.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.
• I have a partial implementation of a function to check if an external is a valid ESM import and inline if not - would that be useful to include in this PR @pi0?

[netlify]

✔️ Deploy Preview for nuxt3-docs canceled.

🔨 Explore the source changes: 46b0ac2

🔍 Inspect the deploy log: https://app.netlify.com/sites/nuxt3-docs/deploys/616fd8b73b1f7c0007c6749d

[pi0]

I have a partial implementation of a function to check if an external is a valid ESM import and inline if not - would that be useful to include in this PR @pi0?

We have some detection system in jiti as well. I think worth doing it later and move logic to mlly and using in externality.