[12.x] Fix infinite rate limiter TTL on custom increments

[paulandroshchuk]

This fixes a race condition in RateLimiter::increment() when the increment $amount is greater than 1.

If the counter key disappears after Laravel checks for it but before the increment() happens, the cache can recreate that key during increment(). When that happens, Laravel needs to write the value back with the proper decay time so the key does not live forever.

The bug was that this recovery logic only checked for == 1. That works for the default increment, but not for calls like increment(..., 5), where the recreated value is 5. This change checks against $amount instead, so custom increments also get the correct TTL.

See #20684 for additional context.

[github-actions]

Thanks for submitting a PR!

Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.