Use message based TestNG formatter

[mpkorstanje]

🤔 What's changed?

Replace the TestNGFormatter with the message based implementation from cucumber-junit-xml-formatter. This achieves several goals:

• Move the internal code base away from the events from the plugin module.
• Extract common parts of Cucumber into modules that can be shared.

This results in several changes/improvements:

1. Use the long naming strategy to include the scenario name, examples group and example numbers.

Feature: Examples Tables
  Scenario Outline: Eating cucumbers
    Given there are <start> cucumbers
    When I eat <eat> cucumbers
    Then I should have <left> cucumbers
    Examples: These are passing
      | start | eat | left |
      |    12 |   5 |    7 |
      |    20 |   5 |   15 |
    Examples: These are failing
      | start | eat | left |
      |    12 |  20 |    0 |
      |     0 |   1 |    0 |

This feature previously contained the examples

 - Eating cucumbers
 - Eating cucumbers_2
 - Eating cucumbers_3
 - Eating cucumbers_4

And will now contain the examples:

 - Examples Tables - Eating cucumbers - These are passing - Example #1.1
 - Examples Tables - Eating cucumbers - These are passing - Example #1.2
 - Examples Tables - Eating cucumbers - These are failing - Example #2.1
 - Examples Tables - Eating cucumbers - These are failing - Example #2.2

2. Rename the suite from io.cucumber.core.plugin.TestNGFormatter to Cucumber

<suite name="Cucumber" duration-ms="61">
  <test name="Cucumber" duration-ms="61">

3. When a scenario is skipped or failed the executed steps are always included in the message element.

<test-method name="Eating cucumbers - These are failing - Example #2.1" status="FAIL" duration-ms="7" started-at="1970-01-01T00:00:00.017Z" finished-at="1970-01-01T00:00:00.024Z">
  <exception class="AssertionError">
    <message><![CDATA[
Given there are 12 cucumbers................................................passed
When I eat 20 cucumbers.....................................................passed
Then I should have 0 cucumbers..............................................failed
]]></message>
  </exception>
</test-method>
<test-method name="Skipping from a step causes the rest of the scenario to be skipped" status="SKIP" duration-ms="5" started-at="1970-01-01T00:00:00.013Z" finished-at="1970-01-01T00:00:00.018Z">
  <exception class="The scenario has skipped step(s)">
    <message><![CDATA[
Given I skip a step.........................................................skipped
And a step that is skipped..................................................skipped
]]></message>
    <full-stacktrace>
      <![CDATA[The scenario has skipped step(s)]]>
    </full-stacktrace>
  </exception>
</test-method>

4. The empty scenario and empty report are considered passing

To be consistent with the exit code of the Cucumber process empty scenarios and test runs are considered passing.

🏷️ What kind of change is this?

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

📋 Checklist:

• [x] Release all dependencies
  • [x] https://github.com/cucumber/junit-xml-formatter/pull/31
  • [x] https://github.com/cucumber/query/pull/39
  • [x] https://github.com/cucumber/testng-xml-formatter/pull/2
• [x] I agree to respect and uphold the Cucumber Community Code of Conduct
• [X] I've changed the behavior of the code
  • [X] I have added/updated tests to cover my changes.
• [ ] My change requires a change to the documentation.
  • [ ] I have updated the documentation accordingly.
• [X] Users should know about my change
  • [X] I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.