[BUGFIX] Avoid using the symfony container to clear its own caches

With the introduction of a custom DI cache in #90418, the container
was used to lookup its own cache and the cache identifier. This
results in bugs if the container cache is stale:
Loading from the cache and flushing the cache will work, but code that
runs after the cache has been flushed (ext_localconf loading) will still
use the a stale container (configuration), as the instance has been
created too early (to be able to clear itself).

Therefore we do now avoid instantiating the symfony container before the
container cache has been cleared.

A positive side effect of this change is that the container cache is
warmed up after the flush.

Releases: master
Resolves: #91114
Related: #90418
Change-Id: I5f10474ab3fab2d17cfdca6cd514b0a95f10bbbc
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64234


Tested-by: Jonas Eberle <flightvision@googlemail.com>
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Helmut Hummel <typo3@helhum.io>
Tested-by: Benjamin Franzke <bfr@qbus.de>
Reviewed-by: Susanne Moog <look@susi.dev>
Reviewed-by: Helmut Hummel <typo3@helhum.io>
Reviewed-by: Benjamin Franzke <bfr@qbus.de>