Re-throw RedisCache::increment errors instead of returning 0

[sascha-egerer]

increment() previously swallowed every \Throwable from the Predis client and returned 0, which every counter caller interpreted as "no hits this window". The exception now bubbles up to Middleware::process() so the configured Config::failOpen policy applies uniformly across infrastructure errors; an E_USER_WARNING is emitted before the re-throw for diagnostic visibility.

[Copilot]

Pull request overview

This PR changes RedisCache::increment() to stop swallowing Predis exceptions (previously returning 0) and instead emit a diagnostic E_USER_WARNING and re-throw, allowing Middleware::process() to apply the configured Config::failOpen behavior consistently across cache infrastructure failures.

Changes:

• Update RedisCache::increment() to emit a warning and re-throw the underlying Redis client exception.
• Update unit tests to assert re-throw behavior and warning emission (including when an error handler throws).
• Document the behavior change in the changelog for the upcoming release.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/Store/RedisCache.php	Re-throws Predis eval() failures after emitting a diagnostic warning; updates method PHPDoc.
tests/Unit/Store/RedisCacheTest.php	Adjusts tests to assert exception re-throw + warning behavior.
CHANGELOG.md	Notes the behavioral change and how it interacts with Config::failOpen.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.