Implement "pulumi state clear-pending-operations"

[Zaid-Ajaj]

Description

This PR implements pulumi state clear-pending-operations as an easier to way to clear pending operations from checkpoint files instead of exporting, editing and importing the stack files.

Fixes #4265. In that issue it is also discussed whether or not pulumi should internally and automatically decide to clear the pending operations. I am personally not sure either about the solution but for the time being at least the users will be able to easily clear the operations themselves without having to edit JSON files by hand.

Checklist

• I have added tests that prove my fix is effective or that my feature works

• I have updated the CHANGELOG-PENDING file with my change

• Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

[lukehoban]

My thinking was that we would address this via the approach outlined in #4265 (comment). Any reason to prefer this approach over that? It seems that the approach noted there takes a lot more of the friction away from users proactively.

[Zaid-Ajaj]

Any reason to prefer this approach over that?

@lukehoban I liked that approach personally but didn't realise it was the consensus as the final solution so I fell back to what the users initially asked for. Also just found out that [engine] Clear pending operations with refresh. partially addresses this issue but it has been open for a while.

I am thinking the following:

• Will resolve the merge conflicts of [engine] Clear pending operations with refresh. and get it in
• Turn pending operations error into a warning and explain that refresh clears pendings operations as per your comment

[lukehoban]

I am thinking the following:

• Will resolve the merge conflicts of [engine] Clear pending operations with refresh. #8435 and get it in
• Turn pending operations error into a warning and explain that refresh clears pendings operations as per your comment

Perfect - sounds like a good plan!

[Zaid-Ajaj]

Closing in favor of #9293