Gherkin 8

[vincent-psarga]

Summary

Preparation for release 4.0
Remove dots-formatter as this uses the Go implementation

This PR goes alongside:

• cucumber-ruby-core#178
• cucumber-ruby-wire#23

Types of changes

• Refactor (code change that does not change external functionality)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I've added tests for my code
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[vincent-psarga]

I agree, but the purpose here is just to illustrate/test the syntax, not necessarily to give a good example of use.

Well, if we can do both at once, I'd say why not :)

It makes me think, I'm wondering about refactoring the existing features inside the features/docs folder so it uses the new syntax.
It can be pretty confusing for the users to have features using the Scenario keyword and the other one using the Example one. Which one is correct ? (well, both of them but still, being consistent would be great).
Same thing for the Scenario Outline.