Cache responses from queue pagination API

[lowellrex]

Implement some way to store responses from the pagination API in state (result sets keyed off of the combination of filters/sorts/pages?) so we don't have to make an API request for all new page requests, filter changes, and re-sorting with a loading spinner when those API requests are in flight. This caching allows us to prevent making additional API calls when the pagination API has already returned a set of tasks that fit on a single page, so we have all of the information we need to apply additional sorts and filters without hitting the server.

Blocked by

• Enable TaskTable to use API requests to filter tasks Enable TaskTable to use API requests to filter tasks #11309 (only makes sense to cache these requests when we are making them)

Acceptance criteria

• Avoid making redundant requests to pagination API.