Description of problem:

useFleetWatchK8sResource hook can return stale data in some cases.

Version-Release number of selected component (if applicable):

All released versions

How reproducible:

Always

Steps to Reproduce:

1. View a VM in the Fleet Virtualization perspective on a managed cluster
2. Navigate to All Clusters in the tree view
3. Within 5 minutes, navigate back to the first VM you viewed
4. Perform an action on the VM, like stop or start, depending on its state.

Actual results:

The status change is not reflected immediately. If you wait, you will see the status be updated in the tree view. Refresh the page to get fresh data.

Expected results:

Change in VM status should reflect immediately on the page.

Additional info:

The hook logic does not attempt to connect to a socket if cached data is less than five minutes old. Instead, we should check if the data is expired before using it as an initial value. We should always connect to an existing socket or open a new one.