CNV-41633: Fix VM list EmptyState on filtering with pod proxy

[upalatucci]

📝 Description

When cluster has proxy pod enabled, the unfilteredData is empty as the proxy pod return empty array from the fetch even if the user just filtered data.

In that case, just watch the selected filters. If we are using the pod for fetching data and the user has selected a filter, don't show the empty state.

Show the empty state if :

unfiltered data is empty if the cluster is not using the pod
if we are using the pod and unfiltered data is empty, check if the user has selected some filters from the query params (no other way to do it )

[openshift-ci-robot]

@upalatucci: This pull request references CNV-41633 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.16.0" version, but no target version was set.

In response to this:

📝 Description

When cluster has proxy pod enabled, the unfilteredData is empty as the proxy pod return empty array from the fetch even if the user just filtered data.

In that case, just watch the selected filters. If we are using the pod for fetching data and the user has selected a filter, don't show the empty state.

Show the empty state if :

unfiltered data is empty if the cluster is not using the pod
if we are using the pod and unfiltered data is empty, check if the user has selected some filters from the query params (no other way to do it )

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[avivtur]

looks very good 👍 just a small comment, and also maybe we want to locate this hook in a general location so other pages use this hook too?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avivtur, upalatucci

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [avivtur,upalatucci]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment