feat: As a user of limit-count, I want to communicate the X-RateLimit-Reset header so my api consumers know when their next allocation window starts, this should be communicated on every response even the rejected response.

[harmseru]

Description

• limit-count plugin does not communicate the X-RateLimit-Reset header only X-RateLimit-Remaining and X-RateLimit-Limit
• There are no X-RateLimit-* headers communicated on a rejected response, here I believe it can be improved to include the X-RateLimit-Reset header as per draft RFC. This header would also be helpful on response of non-rejected(successful) requests

The improvement of this approach would be that consumers of an API know when they can attempt another API call without having to "poll" for sucessful responses with Retries.

[tzssangglass]

I think this could be a good first issue. cc @spacewander

[spacewander]

We need to modify the code to record the time when we start to count.

[mscb402]

please assign to me @spacewander