Askrene query reserve

[Lagrang3]

Adds a new RPC to query the reserves on a given channel.
It is necessary to know the total amount in-flight on a channel to be
able to estimate the channel's liquidity after a failed routing attempt.

For example if a routing request for 1000sat fails in channel "1x1x1:0" and there are no other in-flight
HTLCs in that channel that we know of, we can assume that channel's liquidity is a number below 1000sat.
However, in a similar situation when a routing request for 1000sat fails in channel "1x1x1:0" but we know that
there are two pending HTLCs: one for 1000sat and another for 4500sat, then we may assume that the
channel's liquidity is some number below 1000sat+4500sat=5500sat.

In order to effectively make use of askrene-inform-channel in those situations we need to know the total
value of the reserves combined.

[rustyrussell]

This is racy (well, everything is, but this seems worse than taking reserves into account internally).

Reserves are not guaranteed usage. So, worst case, we should take them into account for maximum, ignore them for minimum?

Which also implies you should clear your own reservations before calling inform, for best results.

Currently in xpay (UNTESTED!) I use inform for failures/successes only. So we can assume this is how it will be used, and so it's sensible to account for reserves internallly?

I also have listreserves implemented, so we can find reserve leaks, but I don't think we should use it for this?

Sorry that I've been piling up stuff in my tree. It's because I've been trying to get xpay to the point where I can test the APIs to assess them properly.

[Lagrang3]

The alternative is to add an API to inform that a "reserve" failed then internally deduce where the liquidity bounds are, ie. max and min, usually max, I think the min is unnecessary.