allow pagination by min_id and max_id

[tateisu]

I want to add "read gap from bottom" feature to my app.

but current API does not support both min_id and max_id is specified.

example:

://mstdn.jp/api/v1/timelines/public?limit=80&min_id=104851024371243870&max_id=104851024489466483
104851024489466483 (max_id parameter)
104851024371243870 (min_id parameter)

response is not in min-max range.
104851030810789863
104851030584864650
104851030520828910
104851030397708486
104851030354767343

Pagination in some Mastodon APIs has no relation between the content ID and the pagination ID.
(example: user's follow list is paginated by follow.id, but it is not exposed in the response.)
in this case the app cannot filter the data using the content ID and pagination ID.

[ClearlyClaire]

I'm not 100% sure this should be called max_id as it is similar to the relation since_id has to max_id, but it is a useful feature and should not break anything.

[tateisu]

API gap reading test (after this PR)
https://docs.google.com/spreadsheets/d/1rDDQbG_vBSVzFsiw1QS2N7DkJD6RFQyFKObc-o17EPg/edit?usp=sharing