include stackTrace in result exception object

[davidjgoss]

🤔 What's changed?

Cucumber Messages now includes a stackTrace prop on the exception object in a test step result. This PR includes that field, which consist of just the captured and filtered stack trace, without the error message.

Also, previously we only tried to parse the stack trace if we needed to filter it - now we always try, because we ideally want to strip the message off the front to populate this new stack trace prop.

⚡️ What's your motivation?

Generally, this is more useful for formatter authors, allowing them to build up a richer representation of an error from messages.

Specifically, we have #2348 where we want this field for the JUnit formatter.

🏷️ 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.

---

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

[coveralls]

coverage: 98.383%. remained the same
when pulling c542af5 on feat/exception-stack-trace
into 567a491 on main.