Upgrade to JUnit 6.0.1 and prevent AOT test scanning failure for JUnit 4 tests #35740
Description
Overview
JUnit 6.0.1 has been released.
While upgrading locally, I discovered that the AOT TestClassScanner will fail if junit.platform.discovery.issue.severity.critical=INFO has been set as a JVM system property. This is due to the fact that the VintageTestEngine is officially deprecated in JUnit 6.0, which results in an INFO level discovery issue.
Luckily, JUnit 6.0.1 introduced a new junit.vintage.discovery.issue.reporting.enabled configuration parameter that can be set to false to disable the Vintage "deprecation" discovery issue. We can therefore prevent AOT test scanning failures for JUnit 4 tests if we set that configuration parameter in TestClassScanner.