[JUnit Platform Engine] Add Surefire naming strategy

[mpkorstanje]

⚡️ What's your motivation?

When testing with Surefire using the long naming strategy the feature name is included in every error message twice. This can be quite annoying when the name is long. For example:

[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.103 s <<< FAILURE! -- in io.cucumber.skeleton.RunCucumberTest
[ERROR] Belly.Belly - a few cukes -- Time elapsed: 0.060 s <<< FAILURE!

Like wise the xml report by Surefire includes the name twice.

<testcase name="Belly - a few cukes" classname="Belly" time="0.06">

By using the cucumber.junit-platform.naming-strategy=surefire property when configuring surefire tests will look pretty in surefire too.

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <version>3.5.2</version>
    <configuration>
        <properties>
            <!-- Work around. Surefire does not include enough
                 information to disambiguate between different
                 examples and scenarios. -->
            <configurationParameters>
                cucumber.junit-platform.naming-strategy=surefire
            </configurationParameters>
        </properties>
    </configuration>
</plugin>

For example:

[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.102 s <<< FAILURE! -- in io.cucumber.skeleton.RunCucumberTest
[ERROR] Belly.a few cukes -- Time elapsed: 0.059 s <<< FAILURE!

And

<testcase name="a few cukes" classname="Belly" time="0.059">

🏷️ What kind of change is this?

• ⚡ New feature (non-breaking change which adds new behaviour)

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct
• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.