[BUG]: When several API revisions exist, publisher does not publish all of them.

[patrickdassier]

Release version

APIOPS v5.0.1

Describe the bug

I found a strange behavior of the publisher when importing APIs with several revision.
This issue is similar to #371.

I have 2 APIM: one is called SOURCE, and the other one DESTINATION
I created an APIs on SOURCE, with only 1 revision.
I ran extractor, completed the PR, ran the publisher, and on DESTINATION, I can find my APIs with its revision => OK

I created a new revision on SOURCE, and set this revision as the current one. I let the old revision online.
So on SOURCE, I have both revision:

• The current one
• Rev 1, that corresponds to the old revision created with the API

I ran extractor, completed the PR, then ran publisher, and on DESTINATION, I only have the current revision, not Rev 1

Expected behavior

I must have both the current revision and the Rev 1 on DESTINATION.

Actual behavior

Only the curren t revision is published, not the preceding one, even if it is online.

Reproduction Steps

See bug description

[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.

[guythetechie]

Will be fixed in our next major release. Closing in favor of #184.