Only use the official Gherkin parser objects and remove custom parser logic

[jsa34]

Going a step further than my previous PR that simply parsed the feature files using the official parser, but then copied this data into the existing parser objects, this PR removes the old parser completely and either uses the data directly that is parsed into the models from the Gherkin parser or adds needed functionality to the Gherkin parser models to enhance just being DAOs for pytest-bdd to use the data as it needs to.

[jsa34]

I'm thinking a different approach might be better to keep the DAO/mapping and logic encapsulated

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sourcery-ai]

We've reviewed this pull request using the Sourcery rules engine. If you would also like our AI-powered code review then let us know.

[youtux]

let's first get #698 merged, then let's focus on this.

Actually, could you rebase this on top of #698, so that in GitHub I can check the diff from that only?

[jsa34]

Closed to focus on parser, and ended up just dumping things I was trying on this branch - apologies!