frontend: Use multiple queries in useKubeObjectList and add support for allowedNamespaces

[sniok]

Create a kubeObjectListQuery, for a singular request
useKubeObjectList can handle multiple clusters and namespaces by using multiple queries

_useKubeObjectList and _useKubeObjectLists are no longer neccessary since useKubeObjectList can handle 1 and more lists

Manual testing done:

• No allowedNamespaces, loads /pods
• two working allowedNamespaces
• one working and one non existing allowedNamespaces
• token auth with access to only one namespace, no allowedNamespaces (fails as expected)
• token auth with access to only one namespace, one allowedNamespaces (works)
• token auth with access to only one namespace, one working and one non existing (works, shows error)
• multi cluster, one cluster with allowedNamespaces[a,b], second cluster with token auth with allowedNamespaces[c] (works)

[joaquimrocha]

Tested and works fine:

• Check cluster regularly, no noticeable differences
• Check cluster with allowed namespaces: only the allowed namespaces are being shown
• Check cluster with the namespaces filtered: only the filtered namespaces show up in the table results

[sniok]

Extracted some logic to a function and added unit tests for it

[illume]

@vyncent-t @skoeva and I are giving this a test...

[vyncent-t]

reviewed the first three commits and left some comments

[sniok]

I've found a bug here, working on a fix

[sniok]

It was recreating connections way too often. Now it's working as expected

Tested by updating a deployment and making sure /deployment and /pods websockets are not recreated

[illume]

Thanks.

Left a few notes about the third commit.

Additionally, the third commit message could use some more detail.

[joaquimrocha]

Tested the allowedNamespaces again and it's still working.

[illume]

👍 thanks