Update orders faster

[anxolin]

Summary

Tries to improve the UX around when we detect an order has been fullfileed.

This PR is a bit sensitive because changes:

• the update logic for pending orders
• the update logic for recently cancelled orders
• the update logic for the check that tells the user if the order is still with a good price (or if they are out of market)

However, the changes try to be scoped to only:

• Update faster (5X) the pending orders --> 2s
• Also the check where we verify if orders are still within the market price (2x) --> 15s
• Additionally, there's a flag to prevent concurrent execution of checks. If there's a previous check onging, the check will be skipped. This rarely occur since checks are fast (way less than 100ms)

For reviewers

I left some commented console logs, was helpful while analysing, but i think is too much output. I left it there cause it's handy imo, but if you totally hate it, i would remove

To Test

1. Make sure pending orders work as expected
   2.Make sure cancelling orders work as expected
2. Ideally, try to reproduce a situation where market conditions change. I think this is hard to test. I guess one way is trying to move the market price (big trade in Uniswap v2) while you are creating a CowSwap order with a very tight slippage tolerance (0.00001%)

context

We need to make sure we detect the trades as soon as possible. Maybe we can research in hybrid approach using (time, bock, events, or a combination of the three). Related #1892

[github-actions]

• 🔭 GP Swap: Gnosis Protocol v2 Swap UI

[elena-zh]

Hey @anxolin , great!
'Open' and 'Filled' statuses are updated faster even than in Order list in Explorer (30 sec there).
'Cancelled' status works as expected.

Orders' status also looks good to me when market conditions change. A nitpick there is that sometimes 'Price out of range' warning may appear for 1 sec on 'Open' order before changing to 'Filled' . See the video (start from 30 sec): https://watch.screencastify.com/v/LlNji6ah7w9oxAfcBWgh

The only issue I found with 'Expired' status: it is still updated in a minute or so

[alfetopito]

Looks good code wise.
I'm not too keen on lot's of logs but we can leave them on and disable if it gets too annoying.

[anxolin]

I'm not too keen on lot's of logs but we can leave them on and disable if it gets too annoying.

I think we log too much, probably we need a better strategy in terms of logs. I feel is more important to make the app be more fluid.

Thanks for the tests @elena-zh, yes, that can happen if the price moves, probably the price moves because of my own trade, so i agree is improvable but it just happens for a few seconds, so we can leave it as it is for now imo.

[elena-zh]

Hey @anxolin , thank you for explanation!
But still 'Expired' status is still updated in a minute or so. I reported a separate issue for this status #1928

The only issue I found with 'Expired' status: it is still updated in a minute or so