Review Nuxt related routing logic based on official migration guidelines

[cnotv]

Description

Our Vue configuration has inherited a lot of Nuxt logic when it comes to require components and routing functionalities.
These are not valid anymore for Vue3 also due the official vue-router migration guidelines.

Details

While compiling on run, the vue.config.js requires a plethora of Nuxt functionalities around the routing logic, which for some reasons fails to retrieve the current route state and breaking abruptly.

Affected files:

• https://github.com/rancher/dashboard/blob/master/shell/plugins/extend-router.js
• https://github.com/rancher/dashboard/blob/master/shell/initialize/client.js#L21 (getMatchedComponents)
• https://github.com/rancher/dashboard/blob/master/shell/utils/nuxt.js
• https://github.com/rancher/dashboard/blob/master/shell/initialize/index.js#L71 (extendRouter)

Possible cause of issue may depends by the getMatchedComponents() implementation.

Example:

[cnotv]

Closing in favor of #11070