Extend test automation for installing plugins to Rancher by using serve and compiled plugins

[cnotv]

Description

Extend current tests, so they will cover cases of a new plugin creation or update since it seemed not to cover critical points.

In a practical perspective, all the used scripts should run successfully:

  "scripts": {
    "dev": "NODE_ENV=dev ./node_modules/.bin/vue-cli-service serve",
    "parse-tag-name": "./node_modules/@rancher/shell/scripts/extension/parse-tag-name",
    "build": "./node_modules/.bin/vue-cli-service build",
    "clean": "./node_modules/@rancher/shell/scripts/clean",
    "build-pkg": "./node_modules/@rancher/shell/scripts/build-pkg.sh",
    "serve-pkgs": "./node_modules/@rancher/shell/scripts/serve-pkgs",
    "publish-pkgs": "./node_modules/@rancher/shell/scripts/extension/publish"
  },

Examples

• defineComponent(): summarized issues with previous/current versions in extension and dashboard, please @rak-phillip feel free to correct https://github.com/rancher/dashboard/issues/10104
• https://github.com/rancher/dashboard/issues/11414
• https://github.com/rancher/dashboard/issues/9537 (needed to be reverted)
• Verify a Harvester cluster dashboard page and its menu items rendered

These tests will simplify and ensure migration does not break existing plugins.

This would help with:

• https://github.com/rancher/dashboard/issues/11049
• https://github.com/rancher/dashboard/issues/10660

[cnotv]

@nwmac this should be done before the migration

[cnotv]

Pushing this out of the Vue3 planning and this milestone as we are testing manually all the extensions commands.