fix: (vue-3) component rendering

[Rirax]

Changes Overview

This PR is a step forward in fixing performance issue with large documents migrating from vue 2 to vue 3.
#5031

Implementation Approach

Our approach is to eliminate the use of Teleport to locate elements in the DOM and the need to render the app each time for each new node.
In the proposed changes we return to an implementation close to that of the vue-2 package.
Vue.extends no longer exists in vue-3, so we've added a renderComponent method to VueRenderer.ts, which reproduces its behaviour

Testing Done

Create a document requiring the rendering of more than 2000 vue components

Verification Steps

Additional Notes

Checklist

• I have renamed my PR according to the naming conventions. (e.g. feat: Implement new feature or chore(deps): Update dependencies)
• My changes do not break the library.
• I have added tests where applicable.
• I have followed the project guidelines.
• I have fixed any lint issues.

Related Issues

#5031

[netlify]

✅ Deploy Preview for tiptap-embed ready!

Name	Link
🔨 Latest commit	c61047e
🔍 Latest deploy log	https://app.netlify.com/sites/tiptap-embed/deploys/66692c3e14bfc40008a111f2
😎 Deploy Preview	https://deploy-preview-5206--tiptap-embed.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[nperez0111]

Very excited to see this thank you @Rirax

I'm not super confident in vue to know where the edge cases might be for something like this. Would it be alright to just put into a beta & see if we get any feedback on it from other users?

[nperez0111]

I think that this approach could potentially help with our react integration as well. I'll need to think on how to actually do that

[nperez0111]

Whoops meant to release on develop not main.
Reverted on main, and cherry-picked to develop