Implement naive caching for queue pagination API

[lowellrex]

Connects #11310. Adds naive caching based only on the URL of the endpoint we are making the task page request to. Later on, we can add the ability to bypass the API request when there is only a single page of results (thus the front-end already has access to all of the rows that the back-end could possibly return so we can do all of the filtering on the front-end without needing to involve the back-end).

In the screen capture below, notice that the second time we make a request for hearing clarification tasks we do not make an API request.

[codeclimate]

Code Climate has analyzed commit bc6caaa and detected 0 issues on this pull request.

View more on Code Climate.

[hschallhorn]

I think we should cache the tasks from viewing the default view (page 1, no filters, no sort) as well, so we don't get the request after clearing the filters in the screen grab

[lomky]

I second the desire to cache our initial empty params tasks too, but happy for that to be in this PR or a follow on!

[lowellrex]

I second the desire to cache our initial empty params tasks too, but happy for that to be in this PR or a follow on!

Will cache initial set of tasks in another PR.