Implemented junit 5 batching

[nbarrett]

Note that this is a resubmission of #3568 with a fix to the version of cucumber tag expressions.

---

• This PR utilises the suite slicing that was originally implemented in serenity cucumber and now implements it with new CucumberBatchTestEngine which is an implementation of HierarchicalTestEngine<CucumberEngineExecutionContext>.

• Example runner class is shown below:

package net.serenitybdd.cucumber.suiteslicing;

import io.cucumber.junit.platform.engine.Constants;
import io.cucumber.plugin.ConcurrentEventListener;
import io.cucumber.plugin.event.EventPublisher;
import io.cucumber.plugin.event.TestRunFinished;
import io.cucumber.plugin.event.TestRunStarted;
import org.junit.platform.suite.api.*;


@Suite(failIfNoTests = false)
@IncludeEngines("cucumber-batch")
@SelectClasspathResources({@SelectClasspathResource("path-1"), @SelectClasspathResource("path-2")})
@ConfigurationParameters({
        @ConfigurationParameter(key = Constants.EXECUTION_DRY_RUN_PROPERTY_NAME, value = "false"),
        @ConfigurationParameter(key = Constants.GLUE_PROPERTY_NAME, value = "com.example.support,com.example.steps,com.example.hooks,com.example.types"),
        @ConfigurationParameter(key = Constants.OBJECT_FACTORY_PROPERTY_NAME, value = "cucumber.runtime.SerenityObjectFactory"),
        @ConfigurationParameter(key = Constants.PLUGIN_PUBLISH_QUIET_PROPERTY_NAME, value = "true"),
        @ConfigurationParameter(key = Constants.PLUGIN_PUBLISH_ENABLED_PROPERTY_NAME, value = "false"),
        @ConfigurationParameter(key = Constants.PARALLEL_EXECUTION_ENABLED_PROPERTY_NAME, value = "false"),
        @ConfigurationParameter(key = Constants.PLUGIN_PROPERTY_NAME, value = "SlicedTestRunner,io.cucumber.core.plugin.SerenityReporter,pretty"),
        @ConfigurationParameter(key = Constants.FILTER_TAGS_PROPERTY_NAME, value = "@my-tag")})
public class SlicedTestRunner implements ConcurrentEventListener {


    @Override
    public void setEventPublisher(EventPublisher eventPublisher) {
        eventPublisher.registerHandlerFor(TestRunStarted.class, event -> {
            setUp();
        });
        eventPublisher.registerHandlerFor(TestRunFinished.class, event -> {
            tearDown();
        });
    }

    public static void setUp() {
        // setup code here
    }

    public static void tearDown() {
        // tearDown code here
    }
}

• CucumberBatchTestEngine depends on objects that were originally in the cucumber-serenity module, but as part of this PR, these were moved out of that module into the serenity-junit5 module as it's not possible for serenity-junit5 to depend on cucumber-serenity, given that there is an existing dependency the other way. So this was done to avoid a circular dependency. This moving of concerns may not be approved by @wakaleo - so I'll let him review and decide. Sorry, I didn't have too much time to work on this as I have work commitments!
• Final disclaimer is that we don't use the junit 5 batching much on the client project given that bazel is used for the bulk of the test parallelism - so try it and see!

[nbarrett]

Sorry, just realised I wasn't against latest HEAD - resubmitting in a moment

[DanielFran]

Are you sure this is needed since it is available in the ParentPom to avoid to define junit5 artifacts version?

[nbarrett]

Yes, you are right @DanielFran - I removed that and all maven targets still ran okay 👍 - repushed and also added in some missing files that mysteriously were missing on last push 🤦

[DanielFran]

Are you sure this is needed since it is available in the ParentPom to avoid to define junit5 artifacts version?

[wakaleo]

@nbarrett I need to roll this change back as the new dependency between serenity-cucumber and serenity-junit5 causes issues in existing projects. The serenity-junit5 and serenity-cucumber modules need to be independent of each other.