Optimize active products (improves navigation performance)

[nwmac]

This PR makes further optimisations to improve navigation performance - primarily optimising the behaviour of the activeProducts getter in the store.

Essentially, rather than always check whether every product is active, we more intelligently only check the top-level products for the app bar and the root products and its child products in the side nav.

Note, this improves performance, so there were a couple of areas where race conditions mean that things worked, where as with the improved performance, they don't.

On note is the call to onEnter - KubeWarden uses this and access the cluster store, but this was being called before loadCluster was called, so cluster schemas were not available.

[richard-cox]

Investigated the issue where refreshing whilst in the KubeWarden extension causes a schema not found error

• auth middleware loads management store --> extension onEnter --> loads cluster store
• the KW onEnter makes a request to cluster resources before cluster store loaded and throws an schema not found error

This does not happen in master

• auth middleware --> setProduct --> currentProduct --> type-map/activeProducts --> "rootGetters${ module }/all" --> mutations.registerType(state, type) will create a cluster store schema section (before load cluster store)
• when KW onEnter then tries to find a schema the cluster schema section exists so no error is thrown

The optimisation in this PR means currentProduct does not call activeProducts and thus the cluster store doesn't get a schema section by the time KW onEnter calls it. TBH this worked by luck, we shouldn't initialise cluster store stuff before the cluster store is set up, and probably need to update kw onEnter given onEnter does not have access to the cluster (we could improve onEnter to handle both post mgmt store and cluster store setup... or improve notifications of this type so extensions can react to other parts of auth middleware process... or something better).

[gaktive]

Once Vue3 is landed, we should revisit if this is required.