docs: route rules options

[Hebilicious]

🔗 Linked issue

❓ 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

I was trying to figure out what static was doing in the route rules, which led me to a deep rabbit hole. I've tried to document my findings in this PR.

📝 Checklist

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

[vercel]

@Hebilicious is attempting to deploy a commit to the Nitro Team on Vercel.

A member of the Team first needs to authorize it.

[Hebilicious]

@pi0 should I close this ? port to v3 ?

[pi0]

Porting to v3 might be better, specially because now route rules are tree-shakable (and extendable by addition option soon!)