After much investigation, the method of local sorting, filtering, and pagination is not feasible due to possible performance issues.

This story takes a different approach in that data will be fetched from AMS (aka subscription) using API-based sorting, filtering, and pagination.  Then, cluster detail information will be fetched from the appropriate cluster endpoint(s) for each result.

After the result of this story - the information for each cluster (both global and regional) will show as expected.  Data refreshing, pagination, filtering, and sorting will all work and be roughly as performant as today even if the user has a large number of clusters.

See: https://miro.com/app/board/uXjVKtbpgaE=/?moveToWidget=3458764597736290807&cot=14 for a rough logic diagram

To test:
The new code will be behind the newclusterlist URL flag.  The goal for testing this story is to ensure the data, sorting, filtering, and pagination is the same between the new cluster list and the current cluster list.

To view the new cluster list:  https://console.dev.redhat.com/openshift/cluster-list?newclusterlist=true
Verify the yellow "New cluster list preview active" banner is showing. 
Verify the yellow "Multiregion preview active" banner is NOT showing

To view the current cluster list: https://console.dev.redhat.com/openshift/cluster-list

Verify the yellow "New cluster list preview active" banner is NOT showing. 
Verify  the yellow "Multiregion preview active" banner is NOT showing