fix(vue): resolve original vue instance

[christian-bromann]

Pull request checklist

With see issues with Vue and Nuxt where importing wrapped Vue components fail because the output target imports a different Vue instance than the original Nuxt project. This is an attempt to resolve the issue. However this is still not an optimal solution as it requires additional work to compile the current approach for CJS.

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally for affected output targets
• Tests (npm test) were run locally and passed
• Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Server side rendering wrapped Stencil components with the Vue output target resolves into:

500
Cannot read properties of null (reading 'ce')

What is the new behavior?

We import the same Vue module as the users uses for their Nuxt application.

Does this introduce a breaking change?

• Yes
• No

Other information

n/a