Fix route match and router route types to fix narrowing and type guard issues

[pleek91]

Description

This PR fixes two bugs which both were causing issues with narrowing router.route either by narrowing the route itself or when using useRoute or isRoute.

Match widening to string

Because CreateRouteOptions['name'] is type string when a route had no name (either by being omitted or by passing an empty string) then Route['matches'][number]['name'] would get widened to string. Would would cause issues for any routes with a no name parent.

To fix this I've implemented the toName both in the types and in the match created within createRoute.

Originally I avoided this because generally the "match" type directly reflects what the user passed in. But we're already adding default values for meta, state, and id is added. So I think having a default value for name also makes sense here.

I did attempt to fix this without modifying the match types and just fixing it within the RouteWithMatch type but that proved difficult (I could get one test case passing but not another).

router.route including no name routes

router.route is a union of all of the route possibilities that could be matched by the router. However this was including no name routes. Which could produce some weird types when doing route narrowing.

To fix this I updated the existing RouterRouteUnion which previously was just a typescript hack to make a distributive type to also filter out routes with no name which makes the type more accurate and also gives it a meaningful purpose.

[netlify]

✅ Deploy Preview for kitbag-router ready!

Name	Link
🔨 Latest commit	aa26c85
🔍 Latest deploy log	https://app.netlify.com/projects/kitbag-router/deploys/6993afb9a67b2b00086ba20a
😎 Deploy Preview	https://deploy-preview-704--kitbag-router.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[pleek91]

These changes didn't seem to effect anything but I do think this is probably good to have.

[pleek91]

I added name and moved options to the beginning. I don't believe moving options to the beginning has any real effect, but this makes sure that the normalized consts will always override anything passed in as options. For example if an id value was passed by a user now it will be ignored. Types would prevent this but we don't want users hacking these sorts of things.