Add details to "step is undefined" error

[vearutop]

🤔 What's changed?

Step text is added to the wrapped error and can help to identify the problematic step.

=== RUN   TestAPISuiteRun/Foo
    suite.go:634: step is undefined: I should have "foo" responssssse with body

⚡️ What's your motivation?

Currently, the error returned for an undefined step lacks details and relies on formatter context to be actionable

=== RUN   TestAPISuiteRun/Foo
    suite.go:634: step is undefined

This makes it hard to understand which exact step is the issue.

🏷️ What kind of change is this?

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

♻️ Anything particular you want feedback on?

No.

📋 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.

[github-actions]

Go API Changes

# github.com/cucumber/godog/formatters
## compatible changes
FlushFormatter: added

# summary
Inferred base version: v0.15.0
Suggested version: v0.16.0

[ahmedaabouzied]

LGTM