Support negatable options to be able to disable settings through the CLI

[stof]

This is mostly useful for the failOn* settings, but it might apply to other boolean settings.

Currently, the CLI flag can turn those settings on if the config file does not, but it cannot turns them off.
We have a use case in the Symfony CI where we want to fail on deprecations by default (including for contributors running it locally) but we have a specific CI job (the one installing the dependencies with --prefer-lowest) where we want to disable it.
Being able to run phpunit --no-fail-on-deprecations to turn off the setting would be perfect, as it means we could turn it on in the config file (making the experience better for contributors running it locally as they would have the expected failures by default)

[sebastianbergmann]

Good catch, thanks.

I will implement

• --do-not-fail-on-deprecation
• --do-not-fail-on-phpunit-deprecation
• --do-not-fail-on-empty-test-suite
• --do-not-fail-on-incomplete
• --do-not-fail-on-notice
• --do-not-fail-on-risky
• --do-not-fail-on-skipped
• --do-not-fail-on-warning

for PHPUnit 10.5, PHPUnit 11.5, and PHPUnit 12.2 shortly. I decided to "backport" this as far back as PHPUnit 10.5 to make migration as easy as possible.

[sebastianbergmann]

After #6236, I will also implement --do-not-fail-on-phpunit-warning.

[OskarStark]

This ticket should also get the label version/10 I guess

[xabbuh]

@sebastianbergmann Thank you very much for this addition. As far as I can see the new options work as expected and will make the migration to PHPUnit > 9.6 for Symfony even easier. ❤