Use the result type 'ambiguous' for ambiguous step matches.

[brasmusson]

Description

Cucumber-Messages has a separate test step result status 'AMBIGUOUS', therefore cucumber-ruby should use the test result type 'ambiguous' for ambiguous step matches.

This is specifically needed for cck v22 conformance where examples with ambiguous step matches are included (#1806).

Requires cucumber-ruby-core#311

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds new behaviour)
• If your change may impact future contributors, explain it here, and remember to update README.md and CONTRIBUTING.md accordingly.

Please add an entry to the relevant section of CHANGELOG.md as part of this pull request.

Checklist:

Your PR is ready for review once the following checklist is
complete. You can also add some checks if you want to.

• Tests have been added for any changes to behaviour of the code
• New and existing tests are passing locally and on CI
• bundle exec rubocop reports no offenses
• RDoc comments have been updated
• CHANGELOG.md has been updated