IBX-764: Added Kernel / Repository Test API

[Steveb-p]

Question	Answer
JIRA issue	IBX-764
Type	improvement
Target eZ Platform version	v3.3
BC breaks	no
Doc needed	yes/no - depending on whether we feel ok with exposing the test base right now No, only internal use

Adds IbexaTestKernel & IbexaKernelTestCase as base for other packages for wholesome integration tests.

The main selling point of those tests is that they also test our service declarations. They are also easy to expand upon by adding more bundles / services into the test Kernel, and makes use of built-in service compilation (which makes the tests faster).

Potentially, by using WebTestCase from Symfony, even routes can be tested.

Addition of MySQL and Postgres tests will be done in a following PR

Current integration tests remain unchanged and will be adjusted in following PRs.

Supports Postgres integration tests

Due to issues with MySQL / MariaDB images those tests can be enabled in a separate PR.

Security hotspots reported by Sonar

False-positives. They're related to md5 usage when creating a hash for temporary directory that stores compiled Kernel.

Other changes

To allow tests with different environments to produce different Kernels, whole environment is used to calculate cache hash. This allows for multiple tests to be run on a local machine, without issues coming from Kernel cache file re-use.

Checklist:

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

[alongosz]

I need to see a consumption example by 1st party package.
The major issue however I have with this solution is a cyclic dependency on ezplatform-core. While it might not be visible atm, it always causes composer installation issues at some point.

[alongosz]

In general this needs to be split into 2 or 3 parts:

1. Namespaces should be introduced to ezpublish-kernel:7.5 since EOM is March 2022, so there's 100% chance that we will need it there anyway
2. Fixer changes (maybe with what I mentioned in the diff comment that follows) need to be separated
3. Repository Test API changes need to be separated (IBX-764)

2 & 3 can remain in this PR but as separate commits. In this case mark the PR as [FAST FORWARD MERGE] and add relevant label.

[Steveb-p]

@alongosz extracted PHP namespace changes to ezsystems/ezpublish-kernel#3111, since they should be merged up from ezplatform 2.5.

EDIT: Converting to draft to prevent accidental merge.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[Steveb-p]

Merged into master in 57c5099.