POST /api/order cancel should include current status

[jerryfletcher21]

Describe the bug
It is not a bug, it is a security improvement (for the client).
When a POST requests is make to /api/order with action cancel, the order is cancelled. Depending on the current status of the order, a penalty may be inflicted on the canceller. The point is that the client can not be 100% percent sure that the current status of the order is the one it think it is. A public order may for example have been taken after the last request of the client to get the current status.

By adding a new parameter in the requests, (current_status for example), the client specifes the status in which it wants to cancel the offer. The server then proceeds in cancelling the offer just if the current status is the one specified in the request, if not it simply returns an error saying that current status is not the correct one.

To Reproduce
Make a POST requsts at /api/order with action cancel

Expected behavior
Prevent the client from cancelling an offer in the wrong status

[Reckless-Satoshi]

This is a great solution to the problem 👍 It is rare, but it can happen in our official client that a maker cancels the order while still public and by the time the request hits, a taker has shown up, therefore making the maker lose his bond without any previous notification and no recourse.

Implementing this fix on the backend and client is rewarded with ⚡ 100K Sats ⚡ (60K Sats for a PR with a backend only fix, and 30K Sats for a PR with client only fix)

[aftermath2]

@Reckless-Satoshi I think I can start working on this, could you assign me?

[jerryfletcher21]

Hello @aftermath2, I have made a PR that implements this fix on the backend. I am not familiar with frontend sutff, you can work on the frontend if you want.

[aftermath2]

@jerryfletcher21 I've already made the changes to the backend and frontend (PR), sorry I didn't know you were working on it.

[jerryfletcher21]

@aftermath2 ah that is a bit unfortunate that we both worked at the backed. Let's wait for @Reckless-Satoshi's feedbacks and then we may do a a single pull requests.

[Reckless-Satoshi]

Haha, okay this is a failure guys! 😄 🤣

To not over-complicate things, we'll merge #1326 but there is a few things from #1325 that make sense to incorporate. More details on #1325 #1326 reviews.

[aftermath2]

@Reckless-Satoshi Just rebased to main to pull the latest changes, resolved a conflict and ran the tests. I think the issue is ready to review, let me know if there are further changes needed.