Paginated Tasks: Work with design to make sure they're happy with the look and feel

We whipped up frontend pagination as a stopgap to let people use the UI when they had a lot of resources. Design and product were lightly involved, and have since brought up some issues to be addressed at a later date:

- Paginated pages use system scrollbars, no dapper scrollbars
- Paginated pages still scroll vertically, even when accounting for pagination
- Resource cards are based on the old system, not the new pagination

Now seems to be the later date when we should address them. Now that we've got a general pattern for pagination across many different resources, it would be a good idea to iterate on the design so that it matches our current design team's goals, so that as we convert frontend pagination to backend pagination, we can have a consistent look and feel.

---
Do we store the things we've already fetched?
How do we show the # of pages?
Do we fetch things on-demand or pre-fetch? On Demand
How many resources per page do we want to show? 10? If more, show a scroll bar?
Do we want to cancel requests that are in-flight if the user clicks next, next, next....