refactor: set new expiresat on each request

[apapazisis]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

The expiresAt field is not updated while new requests are sent.

Issue Number: N/A

What is the new behavior?

The expiresAt is updated on each request. That way we always calculate a new expiration time.
As an example if I have limit:2 and ttl: minutes(1) a bot which sends multiple requests will be blocked and as long as it continues to send requests will be blocked(429 error). The rate limit should go to 2 requests per minute to release the block(429 error).

Does this PR introduce a breaking change?

• Yes
• No

Other information

[micalevisk]

you can convert this PR to draft instead.

or, this this is ready:

• revert the changes made on package-lock.json (tip: use npm ci instead of npm i next time)
• remove the console.log left in the code
• revert the changes made on test/app/app.module.ts file. I guess?