feat: new lp interface (PRO-760 PRO-743 PRO-686)

[AlastairHolmes]

Replaces the burn and mint functions with update and set position functions and adds order ids.

• "set" removes all liquidity associated with a order id and adds back specified amount (optionally changing the tick/tick range associated with the order id).
• "update" will increase or decrease the amount of liquidity associated with a order id (and optionally move the existing liquidity to a new tick/tick range).

Bouncer has not yet being updated to use the new functions and so will fail.

I have removed some existing rpcs, I intend to replace them with improved versions.

Also need to add auto sweeping although this is not hard any longer.

[codecov]

Codecov Report

Merging #3886 (33081bb) into main (a5205b9) will decrease coverage by 0%.
Report is 2 commits behind head on main.
The diff coverage is 52%.

@@          Coverage Diff           @@
##            main   #3886    +/-   ##
======================================
- Coverage     73%     72%    -0%     
======================================
  Files        367     366     -1     
  Lines      56037   56698   +661     
  Branches   56037   56698   +661     
======================================
+ Hits       40631   40855   +224     
- Misses     13345   13757   +412     
- Partials    2061    2086    +25     

Files Changed	Coverage Δ
api/lib/src/lp.rs	0% <0%> (ø)
api/lib/src/queries.rs	0% <ø> (ø)
state-chain/custom-rpc/src/lib.rs	0% <0%> (ø)
state-chain/pallets/cf-pools/src/weights.rs	0% <0%> (ø)
state-chain/traits/src/liquidity.rs	62% <0%> (ø)
state-chain/runtime/src/lib.rs	39% <14%> (-1%)	⬇️
state-chain/amm/src/common.rs	88% <32%> (-9%)	⬇️
state-chain/pallets/cf-pools/src/lib.rs	51% <47%> (-13%)	⬇️
state-chain/amm/src/lib.rs	54% <50%> (-11%)	⬇️
state-chain/amm/src/range_orders.rs	83% <66%> (-5%)	⬇️
... and 10 more

... and 5 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[martin-chainflip]

This is no longer true, but will show up as the documentation for this storage item.

[linear]

PRO-760 Check range order before burn

Now that we have getRangeOrders, we can re-implement the check that makes sure we have the required liquidity before sending the burn extrinsic.

Also we need to fix a mistake where the burn_range_order function is using AssetAmount instead of Liquidity.

PRO-686 [LP-API] `burn_all_limit_orders` and `burn_all_range_orders`

It should be possible for an LP to burn all their orders instead of having to explicitly burn each one.

PRO-743 Move LP queries into runtime rpc

We should move anything that accesses storage directly (via StorageApi) in the LP api into a dedicated rpc endpoint in the node, and access the state via these runtime rpc calls.

As part of this, we should use dedicated rpc return types instead of defining serialize/deserialize on the amm's Pool types.