update to tell PHPUnit assertions stopped working

[loru88]

I updated the docs to let people be aware of this issue with PHPUnit 11.3

I linked to some alternative libraries and I added a workaround about how to make it work, but feel free to suggest a better description.

resolve Behat/Behat#1618

[acoulton]

@loru88 thanks very much for this and apologies I missed it till now.

I approved the workflows which showed a couple of lint issues, however I also have a couple of small comments / suggestions.

[acoulton]

I'd suggest more like:

Suggested change

	Learn more in the paragraph :ref:`assertion-tools`
	Learn more about :ref:`assertion-tools`.

[acoulton]

I would suggest instead describing / showing an example doing this in a BeforeSuite hook e.g. more like:

use Behat\Hook\BeforeSuite;

class FeatureContext {

    #[BeforeSuite]
    public static function initPhpunit() {
        // If you have multiple suites, you may want to use a static variable to ensure this only runs once.
        (new \PHPUnit\TextUI\Configuration\Builder())->build([]);
    }
}

That has a few advantages:

• It is guaranteed to work in the same place in any Behat project (e.g. doesn't depend on the path to a bootstrap file).
• It doesn't depend on the BEHAT_BIN_PATH const which is arguably not part of our public API - I wouldn't expect it to change, but if it did it would be hard to understand what had broken.
• It inits phpunit much later, nearer the point it might actually be required. So for example if you're running other behat commands or things like --dry-run you won't have the overhead of phpunit booting for no reason.