chore(deps)!: upgrade to utopia-php/cache 4.x

[loks0n]

utopia-php/cache 4.0.0 is a constraint-only release: it moves cache onto utopia-php/pools 2.x, and its own public API is byte-identical to 3.4.0. So this needs no code changes here — only the requirement widening, plus the resulting lock refresh (cache 3.0.0 → 4.0.0, pools 1.0.3 → 2.0.1, telemetry 0.3.0 → 0.4.5).

Needed so that appwrite/appwrite can move to pools 2 — utopia-php/vcs pins cache ^3.0 and blocks resolution.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR upgrades the cache dependency and refreshes its transitive dependency lock entries.

• Changes utopia-php/cache from 3.x to 4.x.
• Updates the lockfile to cache 4.0.0, pools 2.0.1, and telemetry 0.4.5.

Confidence Score: 4/5

This PR should not merge until the declared PHP support is aligned with the new dependency graph or the upgrade is made compatible with PHP 8.2 and 8.3.

The cache upgrade necessarily selects pools 2.x, which requires PHP 8.4, while the root package continues to promise installability on PHP 8.2 and newer.

Files Needing Attention: composer.json, composer.lock

Important Files Changed

Filename	Overview
composer.json	Upgrades cache to 4.x but leaves the advertised PHP minimum below the new dependency graph's PHP 8.4 requirement.
composer.lock	Correctly records the dependency refresh, including pools 2.0.1 and its PHP >=8.4 requirement, which exposes the root constraint mismatch.

Prompt To Fix All With AI

### Issue 1
composer.json:32
**Dependency graph requires PHP 8.4**

When a consumer installs this package on PHP 8.2 or 8.3, the new `utopia-php/cache` 4.x requirement selects `utopia-php/pools` 2.x, which requires PHP 8.4 and causes Composer resolution to fail despite the root `php: >=8.2` constraint.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "chore(deps)!: upgrade to utopia-php/cach..." | Re-trigger Greptile}

[greptile-apps]

Greptile has paused reviews on this repository — it used its 100 free open-source review credits for this billing period. Reviews resume automatically on August 8. To continue before then, an organization admin can keep reviews running past the free credits — those bill as normal usage.