Revoke the previous approved breaking changes if ARM request changes after the previous approval

[qiaozha]

As title, sometimes, service team get ARM signed off from a long time ago and SDK breaking changes review happens soon after that, but cases are common that service team could still need to change something after all the signed offs and ARM will revoke the ARＭ sign off labels, at that time, we should revoke all the approved SDK breaking changes as well.

See Azure/azure-rest-api-specs#24625 for an example. the previous invalid SDK breaking change approve labels cause we fail to run CI check properly, and the PR even get merged with all the SDK generation failed.

[raych1]

@konrad-jamrozik ,

I think the case is same as the API breaking change review and the ARM review. If there are new commits pushed to the PR which has ARM signed off and API/SDK breaking change approved, the corresponding approval labels should be revoked, and the reviewers need to review the new commits.

[konrad-jamrozik]

Related issue:

• Automation doesn't properly reset when new commits are pushed to PRs approved to merge #7650

[qiaozha]

another example, service team make a lot of new changes after the initial approval, and ARM reviewer removed the SDK approved labels, however the bot added it back. Azure/azure-rest-api-specs#26059

which causes some of the SDK breaking changes has not really been reviewed properly.