fix(retry-count): don't leak retryCount between requests

[cvx]

Fixes #442

Issue:

retryCount was incorrectly shared between all requests AND was never being reset to 0.

Notes:

1. This adds a retryCount argument to onRateLimit and onSecondaryRateLimit functions. options.request.retryCount is still available as to not break backward compatibility, but since options.request object is shared between all requests, the retry count in there is shared too, so using it is not recommended! I updated the example in readme to use the new argument.
2. The test for this uses an express server - I wasn't able to replicate the issue with the TestOctokit. Possibly because it handles the request object differently, I'm not sure.

[mutantcornholio]

This seems to be huge. If I got it correctly, this means, that current plugin implementation doesn't work in case of concurrent requests. Can we get back to it?

[github-actions[bot]]

:tada: This issue has been resolved in version 4.3.2 :tada:

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot :package::rocket: