Implement generalized pagination support

It's clear there's a quite a few places we need to use pagination. There should be a lazy generator function that grabs each page as necessary implemented such that it can be used at each place we need pagination (`/v1/search/works.json`, `/v1/users/id/works.json` etc)

Start by locating the client entry points for the `/v1/search/works.json` and `/v1/users/id/works.json` endpoints, then compare how they currently retrieve results. Done means a reusable lazy generator fetches each page only as needed and can be used by both named endpoints and other pagination sites.

Written by the indexing model from the issue text.