…ve lazy objects (HypeMC)

This PR was merged into the 7.3 branch.

Discussion
----------

[DoctrineBridge] Fix resetting the manager when using native lazy objects

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

PR #59913 doesn't seem to work as expected. For example, a simple test like this:

```php
class DoctrineTest extends KernelTestCase
{
    public function testManagerRegistryReset(): void
    {
        $entityManager = self::getContainer()->get(EntityManagerInterface::class);
        $entityManager->close();

        self::assertFalse($entityManager->isOpen());

        $managerRegistry = self::getContainer()->get(ManagerRegistry::class);
        $managerRegistry->resetManager();

        self::assertTrue($entityManager->isOpen());
    }
}
```

fails with:

> There was 1 error:
>
> 1) App\Tests\DoctrineTest::testManagerRegistryReset
> Error: Call to a member function __construct() on false
>
> /project/var/cache/test/ContainerTVZSKa5/App_KernelTestDebugContainer.php:709
> /project/vendor/symfony/doctrine-bridge/ManagerRegistry.php:91
> /project/vendor/doctrine/orm/src/EntityManager.php:534
> /project/tests/DoctrineTest.php:21

Here's the dumped container for reference:

```php
protected static function getDoctrine_Orm_DefaultEntityManagerService($container, $lazyLoad = true)
{
    if (true === $lazyLoad) {
        return $container->services['doctrine.orm.default_entity_manager'] = new \ReflectionClass('Doctrine\ORM\EntityManager')->newLazyGhost(static function ($proxy) use ($container) { self::getDoctrine_Orm_DefaultEntityManagerService($container, $proxy); });
    }

    include_once \dirname(__DIR__, 4).'/vendor/doctrine/orm/src/Proxy/Autoloader.php';
    include_once \dirname(__DIR__, 4).'/vendor/doctrine/persistence/src/Persistence/ObjectManager.php';
    include_once \dirname(__DIR__, 4).'/vendor/doctrine/orm/src/EntityManagerInterface.php';
    include_once \dirname(__DIR__, 4).'/vendor/doctrine/orm/src/EntityManager.php';

    $instance = ($lazyLoad->__construct(($container->services['doctrine.dbal.default_connection'] ?? self::getDoctrine_Dbal_DefaultConnectionService($container)), ($container->privates['doctrine.orm.default_configuration'] ?? self::getDoctrine_Orm_DefaultConfigurationService($container)), ($container->privates['doctrine.dbal.default_connection.event_manager'] ?? self::getDoctrine_Dbal_DefaultConnection_EventManagerService($container))) && false ?: $lazyLoad);

    ($container->privates['doctrine.orm.default_manager_configurator'] ??= new \Doctrine\Bundle\DoctrineBundle\ManagerConfigurator([], []))->configure($instance);

    return $instance;
}
```

cc `@nicolas`-grekas

Commits
-------

5972d98 [DoctrineBridge] Fix resetting the manager when using native lazy objects

Symfony >7.3 generates optimized DI caches for PHP >=8.4 by
using `ReflectionClass::newLazyProxy` (and friends) if available [1].

That means a cache that is generated with PHP 8.4 (e.g. CLI context)
can not be used in a PHP 8.2 process (e.g. Web Context) and therefore
we ensure that the major and minor versions match when reusing
a cached DI container.

This has a drawback that DI caches can not be warmed using
`bin/typo3 cache:warmup` on CLI, when CLI and WEB PHP versions
do not share the same major and minor version, but it's better
than a broken instance.

[1] symfony/symfony#59913

Resolves: #107649
Releases: main, 13.4
Change-Id: Ib27b0f015847fbce81fc42685278c72e8a707aa0
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/90988
Tested-by: Garvin Hicking <garvin@hick.ing>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Garvin Hicking <garvin@hick.ing>
Tested-by: Nikita Hovratov <nikita.h@live.de>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benni Mack <benni@typo3.org>
Reviewed-by: Nikita Hovratov <nikita.h@live.de>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Benjamin Franzke <ben@bnf.dev>

Symfony >7.3 generates optimized DI caches for PHP >=8.4 by
using `ReflectionClass::newLazyProxy` (and friends) if available [1].

That means a cache that is generated with PHP 8.4 (e.g. CLI context)
can not be used in a PHP 8.2 process (e.g. Web Context) and therefore
we ensure that the major and minor versions match when reusing
a cached DI container.

This has a drawback that DI caches can not be warmed using
`bin/typo3 cache:warmup` on CLI, when CLI and WEB PHP versions
do not share the same major and minor version, but it's better
than a broken instance.

[1] symfony/symfony#59913

Resolves: #107649
Releases: main, 13.4
Change-Id: Ib27b0f015847fbce81fc42685278c72e8a707aa0
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/90999
Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

Symfony >7.3 generates optimized DI caches for PHP >=8.4 by
using `ReflectionClass::newLazyProxy` (and friends) if available [1].

That means a cache that is generated with PHP 8.4 (e.g. CLI context)
can not be used in a PHP 8.2 process (e.g. Web Context) and therefore
we ensure that the major and minor versions match when reusing
a cached DI container.

This has a drawback that DI caches can not be warmed using
`bin/typo3 cache:warmup` on CLI, when CLI and WEB PHP versions
do not share the same major and minor version, but it's better
than a broken instance.

[1] symfony/symfony#59913

Resolves: #107649
Releases: main, 13.4
Change-Id: Ib27b0f015847fbce81fc42685278c72e8a707aa0
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/90988
Tested-by: Garvin Hicking <garvin@hick.ing>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Garvin Hicking <garvin@hick.ing>
Tested-by: Nikita Hovratov <nikita.h@live.de>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benni Mack <benni@typo3.org>
Reviewed-by: Nikita Hovratov <nikita.h@live.de>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Benjamin Franzke <ben@bnf.dev>

Symfony >7.3 generates optimized DI caches for PHP >=8.4 by
using `ReflectionClass::newLazyProxy` (and friends) if available [1].

That means a cache that is generated with PHP 8.4 (e.g. CLI context)
can not be used in a PHP 8.2 process (e.g. Web Context) and therefore
we ensure that the major and minor versions match when reusing
a cached DI container.

This has a drawback that DI caches can not be warmed using
`bin/typo3 cache:warmup` on CLI, when CLI and WEB PHP versions
do not share the same major and minor version, but it's better
than a broken instance.

[1] symfony/symfony#59913

Resolves: #107649
Releases: main, 13.4
Change-Id: Ib27b0f015847fbce81fc42685278c72e8a707aa0
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/90999
Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>