Fix: Define Steps produces incorrect cucumber expression for step definition (#28)

[clrudolphi]

🤔 What's changed?

Modified the set of character escapes conducted within the CucumberExpressionSkeletonProvider such that the default set of characters needing escaping are escaped (such as was done within the Regex skeleton provider.

⚡️ What's your motivation?

This addresses the problem identified in GH28 in which empty parentheses resulted in an improper cucumber expression.

🏷️ What kind of change is this?

• :bug: Bug fix (non-breaking change which fixes a defect)

♻️ Anything particular you want feedback on?

@gasparnagy please confirm that these character escapes won't cause other problems with Cucumber expressions and they remain compliant with Cucumber syntax and semantics.

📋 Checklist:

• [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.
• [ ] Users should know about my change
  • [X ] I have added an entry to the "[vNext]" section of the CHANGELOG, linking to this pull request & included my GitHub handle to the release contributors list.

---

This text was originally taken from the template of the Cucumber project, then edited by hand. You can modify the template here.

[clrudolphi]

@gasparnagy please review. My regex skills are not as good as yours.