Fix route components remounting rather than being updated when props change

[pleek91]

Description

This approach builds on what I learned in #439 and fixes the remounting of components when params change. What this does differently is it uses a factory to create a wrapper around the route's component that handles the prop binding, suspense, and async updates. And it stores that wrapper in a store so that it can be reused.

[netlify]

✅ Deploy Preview for kitbag-router ready!

Name	Link
🔨 Latest commit	991e807
🔍 Latest deploy log	https://app.netlify.com/sites/kitbag-router/deploys/6796a09a1792480008105997
😎 Deploy Preview	https://deploy-preview-440--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 site configuration.

[stackoverfloweth]

@pleek91, just wanna make sure I fully understand this change. So RouterView is basically back to it's original form at least in the template. However, that component computed that was re-running when components changes is NOT being called anymore because the props are wrapped around component when it was added to the store?

1. If the user actually navigates away and Vue unmounts our RouterView, do we clear the components from the store? Otherwise when the user comes back, would the store re-use an old instance?
2. We have tests around props reactivity right? I would have been concerned that moving props out of the computed would break that reactivity.
3. Are we still considering the idea of rejections being out of users control?

[pleek91]

@stackoverfloweth
What we're creating and storing here is component definitions not component instances. So vue will create new component instances from these component definitions each time. But I'll update the new test to reflect that.

And we could clear the definitions out but I think it makes more sense to just keep them indefinitely.

[pleek91]

@stackoverfloweth foe the rejections I think for now we should keep them as is otherwise transitions won't work going between routes and rejections.