fix(nuxt): return RenderResponse for redirects

[danielroe]

🔗 Linked issue

#20244 (comment)
resolves #20294
resolves #20432

❓ 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)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This adds an internal way for Nuxt composables to predetermine the type of response from the render handler, rather than directly interacting with event.node.res. It then updates navigateTo handling to use this internal ._renderResponse property for indicating status code, etc. There is space here for improving this, including maybe using h3's sendRedirect method behind the scenes in nitro so we don't have to generate the HTML body, for example.

The hook app:redirected was also only added for the purpose of setting cookies before immediately returning a response. But now app:rendered is just as good a response, and we might consider deprecating app:redirected in favour of app:rendered. Thoughts welcome.

Finally, we resolve an issue with setup functions loading even after a redirect by switching from beforeEach to afterEach, and add a test fixture.

📝 Checklist

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

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[pi0]

Smart solution love it 💯