[BUG] Extractor incorrectly adds new endpoints to all revisions

[koregan42]

Release version

4.10.2

Describe the bug

When extracting an API which has multiple revisions, in order to add a new endpoint, the endpoint is extracted into both revisions.

Expected behavior

The endpoint should only be extracted into the revision where the change was made

Actual behavior

When adding a new Health endpoint to Revision 2, the Health endpoint was also added to revision 1.

Reproduction Steps

Add a new endpoint to Revision 2 of an API, and then run the extractor. Notice that the endpoint is also added to Revision 1.

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[waelkdouh]

@simonTTIS - revisions aren't working properly in ApiOps. Our next major release will fix this.

[waelkdouh]

Closing in favor of #184.