It may be beneficial to apply directly in parent pom what was done in DEV-1938. The default value would be 0 and single projects could change it if needed via a pom property.

In many cases ITs flakiness seems related more to variables outside our control (Selenium or infrastructure quirks) than to actual issues with the underlying functionality being tested or the test-framework
Instead of running a whole build again manually in hopes flaky tests eventually pass, let us give them another chance by re-running them within the same build.
The Maven failsafe plugin option https://maven.apache.org/surefire/maven-failsafe-plugin/examples/rerun-failing-tests.html does precisely that.