feat: accept route name argument getRouteBaseName

[BobbieGoede]

🔗 Linked issue

• getRouteBaseName should accept route.name as string #3401

❓ 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

Resolves #3401

This changes the function getRouteBaseName (returned by useRouteBaseName) to also accept directly passing a route name rather than a full route object. These type for this will narrow if typedPages is enabled, so incorrect usage will cause type checking to fail.

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.