Add unit tests for Namespace filtering in resources

[cnotv]

Description

Ensure namespace filtering from the top bar to apply changes.

Context

Part of the group: #6613

• When a user selects a namespace in the top nav of cluster explorer, then goes to the list view of a namespaced resource such as Deployments, confirm that only resources in the selected namespaces are listed
• After refreshing the page, the namespace filter is still persisted

Required tests

• Assure the selection of the namespace from the top bar to be applied in the store or resource (tbd source file)
• Given a faux resource list from the endpoint, render based on filtered values from the store (example case on Development)
• Ensure localstorage user preference resource saving and loading capabilities

[cnotv]

About the NamespaceFilter component, I must admit that's is extremely difficult to know which type of data it's expected for this component in order to display the options. Because of this it's not easy at all to create a mocked data to display what we want in the test.
Also the test cannot be even started.

These are the "getters" which are expected, but I imagine it's pretty much just data?

• clusterId
• currentStore
• currentProduct
• currentCluster
• 'cluster/all'
• isVirtualCluster
• inStore
• 'management/all'
• 'prefs/get'
• systemNamespaces

Any hint @richard-cox @catherineluse ?
This is keeping stuck since 1 day.

PS: This keeps happening also after copy/pasting what is returned from the store and therefore I'll ignore the data from it.

[cnotv]

Currently all the features related to the filtering process have been tested. The only exception has been to the generation of the options, which are anyhow out of the scope.

[cnotv]

As it looks like to test the view means to test exclusively the population of the markup elements in ResourceTable, this will be handled separated with that component.