fix(vite-dev): replace default Vue import with named

[AndreyYolkin]

🔗 Linked issue

Closes: #583

❓ Type of change

This commit fixes an issue where the default Vue import in Vite was undefined in development mode. To solve this issue, the commit creates Vite transformation plugin, running only in dev mode. It looks for default import and replaces with named. Also it adds named Vue export to the vue dist files.

• 📖 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

I've created 2 sandboxes with and without "patch"

1. Broken
2. Unbroken

Since Nuxt Bridge requires Nuxt 2.16, and Nuxt 2.16 running with Vue 2.7, which is the last minor version of Vue 2, I suppose we can rely on paths of vue dists (vue/dist/vue.runtime.esm.js/mjs) for "patching" them. However we can extend the list of possible files for patching and check if they have default export

I have some difficulties with writing a tests for this fix, because original issue happens only in client dev, but mannually tested with vue-demi, portal-vue, vuetify. I can also add Portal-vue integration in this PR, but I'm not sure about it

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[AndreyYolkin]

I made a review today, tested with "problematic" libraries and can confirm, that Vite 4 solves this issue in more general way. So I'm closing this PR, but it was interesting diving into internals!