Feat/reset interface metadata resolvers

[KevinMartinsDev]

Description

This PR is the second part of the worker mode compatibility audit (see #7918). It implements the Symfony\Contracts\Service\ResetInterface for metadata resolvers and extractors that maintain internal state.

The Issue

Several singleton services in the Metadata component use private arrays as local caches (e.g., $localIsResourceClassCache, $properties). In persistent memory runtimes like FrankenPHP or Swoole, these arrays:

1. Grow indefinitely: Every unique class or property processed adds a new entry.
2. Leak memory: Without a reset mechanism, the RAM usage of the worker increases linearly over time.
3. Risk staleness: In some edge cases, internal state might persist where it shouldn't between different request contexts.

The Solution

By implementing ResetInterface, we allow the Symfony kernel to automatically call the reset() method after each request (when running in worker mode).

• ResourceClassResolver: Clears $localMostSpecificResourceClassCache and $localIsResourceClassCache.
• YamlPropertyExtractor: Clears the $properties cache.

This ensures a "clean slate" for every request, preventing slow memory leaks and ensuring long-term stability for high-traffic APIs.

Context

This fix is part of a global audit performed with Igor-PHP.

[dunglas]

Same here. Ressources must be user/request independant. Clearing this cache between request will have bad performance impact for no benefits.

[KevinMartinsDev]

I understand the performance concern, but the 'private array' approach has two major drawbacks in a Worker context: unbounded memory growth (leak) and state isolation (duplicated RAM usage).

A PSR-16 (Simple Cache) implementation would be the ideal compromise. It is actually more performant in a multi-worker setup.

Shared Warm-up: Only the first worker computes the metadata, others benefit immediately.

Reduced CPU & RAM: No redundant computations or N copies of the same data in memory.

Stateless: The service becomes strictly 'Worker-ready' while keeping metadata persistent.