👓 What did you see?

It seems Maven Surefire reports are no longer generated correctly after upgrading to Maven Surefire 3.5.3.
It always indicates 0 test run.

-------------------------------------------------------------------------------
Test set: io.example.CalculatorTest
-------------------------------------------------------------------------------
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.17 s -- in io.example.CalculatorTest

✅ What did you expect to see?

Tests should be again properly logged inside Maven surefire report

📦 Which tool/library version are you using?

cucumber-java 7.21.1
maven surefire 3.5.3
junit.bom.version 5.12.1

🔬 How could we reproduce it?

This issue is reproducing only using Cucumber JVM, Maven Surefire 3.5.3 and Junit 5.
I've made some separate tests using only Maven Surefire 3.5.3 and Junit 5 and it works fine.
The problem reproduces only when Cucumber is added into the mix.

Steps:
1.) Git clone the following showcase project
https://github.com/fslev/cucumber-showcase

2.) Run Maven command
mvn clean test

Actual:
Though the scenarios were successfully executed, there is no related information inside target/surefire-reports/io.example.CalculatorTest.txt

-------------------------------------------------------------------------------
Test set: io.example.CalculatorTest
-------------------------------------------------------------------------------
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.17 s -- in io.example.CalculatorTest

3.) Downgrade Maven Surefire to 3.5.2
Actual:
Everything works fine now.

📚 Any additional context?

Inside Maven Surefire release notes there are some interesting fixes which may have impacted the way Cucumber works:
https://github.com/apache/maven-surefire/releases/tag/maven-surefire-3.5.3