Add offset and limit to the pagination object

[adathouse]

When fetching multiple batches from a cursor it would be helpful to make the current position in the cursor explicit in the result.

e.g. curl "https://api.congress.gov/v3/bill?format=json&api_key=<<key>>" returns this pagination object:

    "pagination": {
        "count": 421313,
        "next": "https://api.congress.gov/v3/bill?offset=20&limit=20&format=json"
    }

It would be useful to have offset and limit directly in the pagination object so you don't need to parse the URL to get them.

The specific use case I'm working with is tracking the absolute sequence of cosponsors and I need to add the page offset to the list sequence in the result when iterating over multiple cosponsor pages. I'll open another issue to add the cosponsor index as a value in the cosponsor object, since that is useful for tracking the correct ordering for cosponsors.

[adathouse]

Another option that is helpful for data like cosponsors where the order is significant and can cross multiple pages is to just include the index/offset of each item globally across result sets. That's easier than having to calulate where you are in the list. Note this issue mostly arises where the data crosses multiple pages and you need to track the global order.