feat: include exceptions in test step result messages

[davidjgoss]

🤔 What's changed?

• Include exception in the result where there was an error in running a step.
• Use that in the JUnit formatter for the <failure/> tag

⚡️ What's your motivation?

Confirm with latest CCK behaviour, get better parity with JVM's JUnit formatter

🏷️ What kind of change is this?

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

📋 Checklist:

• [x] I agree to respect and uphold the Cucumber Community Code of Conduct
• [x] I've changed the behaviour 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.

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[coveralls]

Coverage: 98.564% (+0.001%) from 98.563% when pulling 1fe8fcb74d31a892b9cc9f952133ea1f71b49518 on exceptions-in-messages into 88eb48d63f0c202d600509d4238694235305b3dc on main.

[Rubea1435]

Can you please explain what's changed in this pull request? I use Cucumber.js since 8.0.0 version and there always have been error messages in step results with error trace.

[davidjgoss]

@Rubea1435 you're right in that the information was there before. It's just now included in a more structured format that makes it more useful to certain reporting tools.