Current situation

We keep a namespace filter that persists across views, but we use it just for filtering the resources on client side.
i.e. we do requests for all namespaces and then we filter the results locally.

Impact

Besides the extra processing needed when more results are returned (due to asking from all namespaces), we may also run into issues where users do not have access to such namespaces (this is related to #679 ).

Ideal future situation

If a namespace (or more) are set for the entire application, we should use them in the queries as well. Maybe this solution should be done together with #679 .

cc/ @callmevladik, @lijianzhi01

This is part of the performance epic #1161