refactor(nuxt): use relative imports into composables

[danielroe]

🔗 Linked issue

❓ 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

I came a significant performance hit (in Nuxt Bridge) from importing from #app alias with vite, because #app re-exports lots of files which themselves import from #app.

We can work around that by using relative imports, which I think is also slightly nicer. Even though I haven't measured a slow-down in this repo, it can't hurt and should be a more intelligible approach for vite. I've left a number of imports from #app untouched within plugins/components as these are not re-exported from #app. (It might also be possible to do the same with head, but it's still in a quasi-independent state and this can wait for improvements to its implementation.

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	eec511b
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/63210b01f766850008b089ca

[pi0]

I don't think it should significantly affect performance unless something is wrong with the intermediate resolver cache. Also entrypoint of app is anyway finally imported. But using relative import paths when possible seems more readable and if it is helping performance, why not :)