feat(p2p): replace order in single packet

[sangaman]

This modifies the procedure for replacing an order in the order book. Previously, it would go like this:

1. Remove old order & send order invalidation to peers.
2. Place new order and wait for matching to complete (which may take
   some time if it involves swap attempts).
3. Send new order to peers.

Now it goes:

1. Put the old order on hold, preventing further swaps/matching.
2. Place the new order and wait for matching to complete.
3. Remove the old order from the order book.
4. Send a single packet to peers with new order info and old order id.
5. Peers that receive this packet will remove the old order and add the new one sequentially.

By default, replaced orders will have the same local order id as the order they are replacing unless a different id is specified.

Closes #1805. Closes #1806.

[raladev]

Commit: a3a70ac

• it seems replace logic does not work for now, just new order is placed to orderbook without removing old one.
  Screenshot from 2020-08-13 13-55-51
  Screenshot from 2020-08-13 13-55-14
  UPD: same for last commit

[sangaman]

I made several fixes and new tests, including some manual testing. I mainly just want to make sure the simulation tests here pass, since I was having some trouble running them locally. I'll check back tomorrow and make sure everything is good with the tests, but in the meantime this is ready for testing/review.

[ghost]

Would it be possible to use the same order id when replacing the order?

➜  xud git:(replace-order-packet) ✗ ./bin/xucli sell 0.001 BTC/USDT 10000 --order_id="abc123" no matches found
➜  xud git:(replace-order-packet) ✗ ./bin/xucli sell 0.001 BTC/USDT 13000 --replace_order_id="abc123" --order_id="abc123"
6 ALREADY_EXISTS: order with local id abc123 already exists

At the moment arby's implementation is using:

`arby-${pairId}-buy-order`
`arby-${pairId}-sell-order`;

as order ids which works against master branch, but fails in this branch.

[raladev]

• utils matching output is still broken
  it prints nothing except of no matches found when match was founded and swap was successful
  Screen utils
  Screen log
• replace with different ids works (~0.2 sec is required to deliver packet to remote node), but if match was founded, replace will be performed only after 20-30 sec (time of swap). So, real testing with arby is required, it can be a bottleneck.

[sangaman]

Would it be possible to use the same order id when replacing the order?

Yes I can try and handle #1806 here as well.

[sangaman]

Replaced orders now use the id of the order they are replacing by default, all tests are passing, and the issue with the cli not displaying matches has been fixed. Thanks!

[ghost]

Works nicely - good job 👍

Tested with arby's ExchangeUnion/market-maker-bot#75 branch