Scope update from @aalves08 (Nov 14th 2024): The goal here is to remove the unload mechanim from the code

Setup

• Rancher version: 2.7.5ish
• Rancher UI Extensions: kubewardn, elemental plus built in harvester-manager
• Browser type & version:

Describe the bug

• When plugins are initially loaded they call generic load functions
• These generic load functions include a call to removePlugin
• This shouldn't be needed on load. I think they were added as part of the dynamic load/unload of the harvester cluster plugin

harvester-manager flow

• vue.config virtualModules --> initPlugin --> removePlugin --> uninstall --> updateMatcher
• vue.config virtualModules --> initPlugin --> applyPlugin --> addRoutes --> updateMatcher

kubewarden and elemental

• shell/plugins/plugin loadPluginAsync --> loadAsync --> element.onload --> removePlugin --> uninstall --> updateMatcher
• shell/plugins/plugin loadPluginAsync --> loadAsync --> element.onload --> applyPlugin --> addRoutes --> updateMatcher

If we can be smarter when callign removePlugin we can chop out some undeeded churn (
removing products, clear model cache, locales, stores, plugin leave functions, and most importantly route changes

To Reproduce

• add both elemental and kubewarden extensions
• refresh on any page