Support PHPUnit 10

[stof]

this is a meta-issue tracking blockers for using PHPUnit 10:

• Migrate to static data-providers #63
• [PHPUnit bridge] Support for PHPUnit 11.1+ symfony/symfony#49069 to support PHPUnit 10 in symfony/phpunit-bridge (that we rely on to report deprecations)
• PHPUnit 10 support? Yoast/PHPUnit-Polyfills#82 to support PHPUnit 10 in yoast/phpunit-polyfills (at least marking it as compatible in the composer constraint)
• Remove usage of onNotSuccessfulTest to mark tests as skipped #65 Removing usage of TestCase::onNotSuccessfulTest to mark tests as skipped as this is not supported anymore
• Making our base TestCase compatible with PHPUnit 10 (TestCase::getName was removed, replacing it with 2 methods instead of having a boolean flag)

[uuf6429]

Regarding the last point, to be clear: getName() got renamed to name() (not removed). I didn't get what was meant with two methods instead of flag, though. If that can be clarified, someone could maybe implement that change already.

[stof]

Well, the last point is not the hard block. Migrating to the new method will be easy. But it is not high priority as long as the other points are not resolved.

[uuf6429]

I'll consider jumping into some of those tasks.

On a totally unrelated sidenote, there are plenty of finished things ready to be merged (some of which are blocking the classic-webdriver) - what's the situation in general? Is it ok to merge my own PR given review approval?

[aik099]

symfony/symfony#49069 to support PHPUnit 10 in symfony/phpunit-bridge (that we rely on to report deprecations)

@stof , The issue was merged. Maybe we can proceed with PHPUnit 10 support now?