[BUG] Publish with last commit is same as publish with all commits

[roshair]

Release version

6.0.1.7

Describe the bug

When deploying with publish-with-last-commit option, apiops deploys and re-creates all the resources like apis, subscriptions etc. Also, all the changes which might have been done in multiple commits, are done. There is no difference between publish-with-last-commit and publish-all-commits option. This is just creating confusion for users and adding complexity.

Expected behavior

Publish with last commit will work faster as compared to all commits and deploy changes only, not the entire repository comparison.

Actual behavior

It compares the entire repository, re-creating all the resources one by one.

Reproduction Steps

1. Add multiple changes in commits.
2. Run publisher pipeline with deploy to last commit.
3. It will re-create all the objects in the repository one by one

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

[roshair]

It is not linked to #774 these are two different scenarios. Do I manually need to paas commit ID? I am passing the commit ID as provided in the example