… (HypeMC)

This PR was merged into the 6.4 branch.

Discussion
----------

[HttpClient] Fix `reset()` not called on decorated clients

| Q             | A
| ------------- | ---
| Branch?       | 6.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

This was broken in #49513 for the main HTTP client and, as far as I can tell, never worked for scoped clients. The problem is that some decorator clients, like the `ThrottlingHttpClient`, have their own `reset()` method, which never gets called when using the `services_resetter` service. Scoped clients don't decorate the main one but instead use it as a dependency.

Commits
-------

8f5f98a5631 [HttpClient] Fix reset not called on decorated clients

…ervice resetter

…nerated by optional cache warmers

…s-grekas)

This PR was merged into the 6.4 branch.

Discussion
----------

[Cache] Don't clear system caches on `cache:clear`

| Q             | A
| ------------- | ---
| Branch?       | 6.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        | Fix #59445
| License       | MIT

As spotted by `@MatTheCat` in symfony/symfony#59445 (comment), non-optional cache warmers currently cannot use any cache pools derived from the `cache.system` one.

The reason is that when running `cache:clear` with no `var/cache` folder, we skip running those cache warmers since they already ran to execute the command, but we still call the cache clearer service, which empties system pools at the moment, annihilating anything non-optional cache warmers put in these pools.

I propose to fix this by just not clearing cache pools derived from the system pool anymore. System pools are meant to we stored in the `kernel.cache_dir` anyway, so they're already cleared when `cache:clear` empties that folder.

Commits
-------

8e820561295 [Cache] Don't clear system caches on cache:clear