The reset limit backoff code may not be timezone aware

First of all a great useful action… been using it for multiple projects. For the first time I tried using it on a self hostet runner and faced this rare issue hence reporting. This is also the first time that I have faced the rate limiting response form GHA and I get a feeling that the code for retry backoff reset may not be timezone aware… see the attached log. Note the very last line shows that that next attempt will happen 5Hr 30 mins and 59 seconds later. though the authors intention is to try 1 minute later

Since this self hosted runner is running in India time which 5.5 hrs ahead of UTC… it is clearly a bug that instead of retrying after 1 minute it is adding the time zone offset as well.

  2022-02-24 21:15:38 +0530 - publish -  INFO - created check https://github.com/Apra-Labs/ApraPipes/runs/5321272796
  2022-02-24 21:15:38 +0530 - publish-unit-test-results - WARNING - Request GET /search/issues?q=type%3Apr+repo%3A%22Apra-Labs%2FApraPipes%22+e10e0c3b16257b9be2a05ed3df65554798615562&per_page=100 failed: Forbidden
  2022-02-24 21:15:38 +0530 - publish - WARNING - Request GET /search/issues?q=type%3Apr+repo%3A%22Apra-Labs%2FApraPipes%22+e10e0c3b16257b9be2a05ed3df65554798615562&per_page=100 failed with 403: Forbidden
  2022-02-24 21:15:38 +0530 - publish-unit-test-results -  INFO - There is no Retry-After given in the response header
  2022-02-24 21:15:38 +0530 - publish-unit-test-results -  INFO - Response body indicates retry-able error: you have exceeded a secondary rate limit. please wait a few minutes before you try again.
  2022-02-24 21:15:38 +0530 - publish-unit-test-results -  INFO - Reset occurs in 5:30:59.330597 (2022-02-24 21:16:38), setting next backoff to 19859.330597s

[EnricoMi]

Can you please test the fix?

uses: EnricoMi/publish-unit-test-result-action/composite@branch-fix-reset-timestamp-utc

[EnricoMi]

Thanks for reporting, this is valuable. I will look into this.