API Selectively register test folder in manifest

[maxime-rainville]

Parent issue

• PHPUnit9.5 detecting and crashing on PHPUnit 5 test #10146

[maxime-rainville]

This is still a work in progress, but most of the needed logic as been implemented ... it's just a question of updating Kernel and the Manifests to use it.

A question worth pondering is what we do with PHPUnit version 4, 6, 7, 8 or 10. Right now, I'm treating those as "unknown" ... this means those test will be included when running PHPUnit 5 and excluded when running PHPUnit 9. If we add support for PHPUnit 10 in a later release, we'll have to tweak this logic again.

A thing to note is that the new logic will only apply to tests folders that are at least 3 levels down (aka inside the vendor folder) ... if you write your tests using the PHPUnit 5 API and decide to install PHPUnnit 9, I'm not sure what we can do for you.

[emteknetnz]

Approach looks great

I think the term 'CI Library' sounds, weird/wrong? Something along the lines of "Module test folder' is more correct?

[maxime-rainville]

Ready for (hopefully) final review.

• I've rebased back on the 4 branch
• I've renamed everything from CiLibrary to CiConfig
• Module::getCIConfig() now returns an arry.
• I've add regex after the constraint check to cover things like 1.2.3, ~1.2.3, 1.2.*. Added more unit tests to cover those extra edge cases.

[maxime-rainville]

I've implemented @michalkleiner suggestions.

[emteknetnz]

Merge on green