Fix executing Specs tests via JUnit Platform and Vintage engine Prior to this commit, the JUnitPlatformTestExecutionListener parsed the uniq…
Fix executing Specs tests via JUnit Platform and Vintage enginePrior to this commit, the JUnitPlatformTestExecutionListener parsed theunique ID to determine the class and method name for TestIdentifierswithout children but with a ClassSource. This occurs when a Spock testclass uses `@Unroll` on all its test methods. However, other testingframeworks such as Specs2 don't provide a unique ID that is parseablewhich lead to the methodName being null which cause a failure duringserialization. The effect was that tests hung because the build VMwas waiting for the worker to finish the tests it started.The Spock-specific workaround in our listener is now replaced with amore robust one that always uses the methodName provided by the JUnitPlatform instead of parsing it.