Add support for the RateLimit-Reset header

[maxprokopiev]

https://tools.ietf.org/id/draft-polli-ratelimit-headers-00.html#rfc.section.3.3

Lots of APIs use a set of 3 RateLimit-xxx headers:

RateLimit-Limit: containing the requests quota in the time window;
RateLimit-Remaining: containing the remaining requests quota in the current window;
RateLimit-Reset: containing the time remaining in the current window, specified in seconds or as a timestamp;

where RateLimit-Reset can easily be greater than Retry-After (no idea why, I guess it's up to the developers of the API).

What do you think about adding support for that header along with Retry-After?

[olleolleolle]

This change looks solid, and useful!

[olleolleolle]

Nicely added resource URLs!

[maxprokopiev]

@olleolleolle thank you for the lightning fast review ✨ in df7f0f3 I've also added a small change to the readme

what's the release process of the gem? should I just merge this one and you handle the rest? (update: I clearly can't merge this 😅 since I just have read access)

[olleolleolle]

@maxprokopiev Features, like this PR, get review, perhaps by multiple readers, then are merged. That's the PR.

Then, a short, mostly automated procedure for getting a release out is done by a maintainer.

If the repository has a CHANGELOG document at all, it'll be a nice thing to create a log line for it, so that the releasing person can use that in descriptions, but if no such document exists, we use other automated tools to make a GitHub Releases "What's Changed?" snippet of text.

Hope this clarifies!

[maxprokopiev]

good to know, @olleolleolle thanks for the explanation and for merging this!

[olleolleolle]

@maxprokopiev The main branch will be cut as 2.0.0, I think, since it contains breaking changes (keyword arguments-in-middleware-related, see CHANGELOG.md). Investigating!