feat(routeRules): allow wildcard redirects

[JaZo]

🔗 Linked issue

#1748

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 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 PR adds support for wildcard redirects in routeRules:

  routeRules: {
    '/wildcard/**': { redirect: { to: '/wildcard-2/**', statusCode: 301 } },
  },

It also keeps query parameters, just like the proxy does.

Resolves #1748.

📝 Checklist

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

[manniL]

This is a good start! But we also need to add custom rules here for Netlify/Vercel/... redirect files 🤔

[JaZo]

Ahh the presets, yes! Forgot about them as we don't use any of those. I'll see if I can add this, but that will probably take a while.

[pi0]

Good point regarding platform support. It is not necessary however we can iterate and support it later in the future as mainly nitro server should be able to (universally) catch any platform-unsupported patteren.

[manniL]

@pi0 I agree. Happy to add it later and let nitro handle it for now 👍🏻

[JaZo]

I've added examples to the documentation, added tests and implemented Netlify and Vercel as these tests failed!

[nuxt-studio]

✅ Live Preview ready!

Name	Edit	Preview	Latest Commit
nitro	Edit on Studio ↗︎	View Live Preview	521114d

[pi0]

Thanks for quality changes ❤️