[Composer] Fixed failing integration tests

[alongosz]

Question	Answer
JIRA issue	n/a
Requires	ezsystems/ezplatform-kernel#387
Type	feature/bug/improvement
Target Ibexa version	v3.3+
BC breaks	no

For more details about the failure see ezsystems/ezplatform-kernel#387. Here I managed to get this working by smaller changes than anticipated:

• Added league/flysystem-memory as some tests are executed using the new IbexaTestKernel and require it.
• Added symfony/proxy-manager-bridge to resolve circular reference exception
• Disabled process timeout for integration tests, the same way kernel does.

Known issues

As stated in ezsystems/ezplatform-kernel#387, we need to rethink the way we had those tests organized. It seems we need some more common shared search base tests so we don't rely on tests from kernel (by principle PHPUnit tests are not supposed to be executed externally). Maybe ibexa/test-core is a good place for that, but then it would be for Ibexa 4.x+ only.

I've also spotted locally the following E_NOTICE level error:

1) eZ\Publish\API\Repository\Tests\SearchEngineIndexingTest::testIndexContentWithNullField
Undefined property: stdClass::$content_name_s

./lib/ResultExtractor/NativeResultExtractor.php:56
./lib/ResultExtractor/NativeResultExtractor.php:36
./lib/ResultExtractor.php:188
./lib/ResultExtractor.php:70
./lib/Handler.php:154
./vendor/ezsystems/ezplatform-kernel/eZ/Publish/Core/Repository/SearchService.php:179
./vendor/ezsystems/ezplatform-kernel/eZ/Publish/Core/Repository/SearchService.php:98
./vendor/ezsystems/ezplatform-kernel/eZ/Publish/SPI/Repository/Decorator/SearchServiceDecorator.php:33
./vendor/ezsystems/ezplatform-kernel/eZ/Publish/Core/Repository/SiteAccessAware/SearchService.php:54
./vendor/ezsystems/ezplatform-kernel/eZ/Publish/API/Repository/Tests/SearchEngineIndexingTest.php:618

Seems CI has different error reporting settings, so leaving this one for later. The production code needs to trust less in the response fields returned by Solr Gateway.

Checklist:

• Provided PR description.
• Tested the solution manually.
• Provided automated test coverage.
• Checked that target branch is set correctly (main for features, the oldest supported for bugs).
• Ran PHP CS Fixer for new PHP code (use $ composer fix-cs).
• Asked for a review.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication