feat(nuxt): add dev reviver for VNode and do not deduplicate server/client logs

[danielroe]

🔗 Linked issue

resolves #27130

📚 Description

Because Vue calls console.warn when stringifying a Vue component, it will trigger an infinite loop if consola is wrapping console when stringifying a Vue warning. Non-Nuxt issue/example here: unjs/consola#298.

For now, given how common it is for Vue to warn about non-existing components (a typo is sufficient!) I think the best solution is just to remove the ability to deduplicate server/client logs, which means users may get duplicate logs.

We can revisit later if we implement loop protection upstream.

I've also added another reducer/revivers only for logs, which handles VNode type. Other ideas to improve DX would be welcome.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.