Add micro-api-client pagination

[bcomnes]

- Summary

This still requires the pagination parameters to be added to open-api.

- Test plan

We should have a test server and make sure we get the right shape back.

- Description for the changelog

Adds pagination data to paginated responses.

data.pagination = { next: 2, last: 2, current: 1, total: null }

[bcomnes]

WIP till I there are some tests on this. Also, this is going to be a really bad breaking change.

[coveralls]

Coverage increased (+0.001%) to 66.462% when pulling 13c116f on pagination into 64c68b5 on master.

[coveralls]

Coverage increased (+0.07%) to 66.531% when pulling 9a0f057 on pagination into 6070f83 on master.

[bcomnes]

Maybe we can do this without a breaking change, adding pagination as an array property? Kind of weird but would ease the pain.

[bcomnes]

Ok, I modified this to not be a breaking change. What do you think @DavidWells ?

Also, the total value is blank because bitbaloon does not return X-Total-Count. Maybe we should have the pagination calculate this?

I'm a little less satisfied with the shape, (adding a property to an array instead of returning an object), but it lets us add this without a breaking change, and it shares the same algorithm as micro-api-client.

[swyxio]

seems unobjectionable. but i have v little contextual knowledge to be of use here.

[bcomnes]

I spoke with @DavidWells last week over DM. Sounds like we should have a chat this week about this. He suggested we aim for the ideal API shape. I agree, though I worry we'll never get around to it due to the pain / refactoring involved. If we take an iterative approach, (e.g. the array property), we could at least gain the benefit of this without jumping that hurdle now. But it would also increase the probability of never refactoring to get to the ideal shape.

[swyxio]

we never got around to this :(

[bcomnes]

FWIW, this is a working solution.

[JGAntunes]

Addressed via #283, further discussion in #285. Thanks for the work you've put into this 🙌