fix(nuxt3): move new router behavior to useActiveRoute

[danielroe]

🔗 Linked issue

resolves nuxt/nuxt#13630

❓ 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

Follow-up on #4092; users may legitimately wish to access current route within the page that is displaying. It doesn't make sense to suspend the route within the page that is loading, even if we do so elsewhere.

This PR provides the current route to the children of NuxtPage, exempting them from the suspension behaviour, meaning effectively useRoute only suspends the routes outside pages (e.g. in layouts or app.vue)...

An alternative/future approach would be to allow users to be in full control of this behaviour, perhaps allowing useRoute to take an option to enable the suspension behaviour for that route alone. Thoughts welcome.

📝 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	f234ad4
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/624d8b2c61a39e00087ab303

[misaon]

Thanks @danielroe ! 👍🏼

[pi0]

There is too much overhead by injecting this way also makes useRoute behavior inconsistent. I propose that we introduce the new behavior of #4092 as the new useActiveRoute composable which changes after suspense.