BUGFIX: ensure PHPUnit exists only as dev dependency

[skurfuerst]

I am currently experimenting with Pest PHP (and specially Playwright based Browser testing) - and this prevents me from installing Pest :-)

[skurfuerst]

Update: I would like to pursue this, but this will lead to followup problems - so I am not sure it is worth it:

  Problem 1
    - Root composer.json requires neos/flow-development-collection 9.0.x-dev -> satisfiable by neos/flow-development-collection[9.0.x-dev].
    - Root composer.json requires pestphp/pest ^4.0 -> satisfiable by pestphp/pest[v4.0.0, ..., 4.x-dev].
    - brianium/paratest[v7.11.2, ..., v7.13.0] require symfony/console ^6.4.20 || ^7.3.2 -> satisfiable by symfony/console[v6.4.20, ..., 6.4.x-dev, v7.3.2, ..., 7.4.x-dev].
    - brianium/paratest[v7.14.0, ..., 7.x-dev] require symfony/console ^6.4.20 || ^7.3.4 -> satisfiable by symfony/console[v6.4.20, ..., 6.4.x-dev, v7.3.4, ..., 7.4.x-dev].
    - pestphp/pest[v4.0.0, ..., v4.0.4] require brianium/paratest ^7.11.2 -> satisfiable by brianium/paratest[v7.11.2, ..., 7.x-dev].
    - pestphp/pest v4.1.0 requires brianium/paratest ^7.12.0 -> satisfiable by brianium/paratest[v7.12.0, ..., 7.x-dev].
    - pestphp/pest v4.1.1 requires brianium/paratest ^7.14.0 -> satisfiable by brianium/paratest[v7.14.0, v7.14.1, v7.14.2, 7.x-dev].
    - Conclusion: don't install one of nunomaduro/collision[v8.8.2], symfony/console[v6.4.27] (conflict analysis result)
    - Conclusion: don't install one of nunomaduro/collision[v8.8.2], symfony/console[v6.3.12] | install symfony/console[v7.3.5] (conflict analysis result)
    - Conclusion: don't install pestphp/pest v4.1.2 (conflict analysis result)
    - Conclusion: don't install pestphp/pest v4.1.3 (conflict analysis result)
    - Conclusion: don't install symfony/console[v7.4.0-BETA2] | install one of symfony/console[v6.3.12, v6.4.27] (conflict analysis result)
    - Conclusion: don't install symfony/console[v7.3.5] | install symfony/console[v6.4.27] (conflict analysis result)
    - Conclusion: install nunomaduro/collision v8.8.2 (conflict analysis result)

[mhsdesign]

The symphony conflict you showed is a general problem as we use outdated symphony components which needs to be updated because seemingly everyone wants them in some version -> that a dev dependency dictates the version of symphony console which is to us a regular runtime dependency is a mistake of pest as this just calls for trouble - pest should either namespace symphony console or dont introduce a framework for cli handling.

Regarding the problem with PHPUnit: I agree with this change as this is basically a followup to my #5592 which already relaxed php unit constraints when the neos/contentrepository-testsuite is installed as otherwise i would not be able to use the behat step definitions in my custom project where i have already a never version of phpunit installed.

I already mentioned in #5619 that we should discuss a more stable solution for our new dev dependency packages and dev dependency handling of the collection as this is now the 3rd change which attempts to hotfix something :D
Id be up for a sync to hopefully tackle the full "where do we define dev dependencies" once and for all ... cc @kitsunet ?