feat: add redeeming to LP API

[j4m1ef0rd]

Pull Request

Closes: PRO-959

Checklist

Please conduct a thorough self-review before opening the PR.

• I am confident that the code works.
• I have updated documentation where appropriate.

Summary

TODO: Add new command to the docs

• Didn't add this command to the bouncer test. Would be quite a bit of work to do the full redeem flow or reuse any of the fundRedem test code. Not sure if it's worth the time.

Sample usage, redeem all:

curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "lp_request_redemption", "params": ["0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266", null, "0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266"]}' http://localhost:10589

[dandanlen]

I think if we want to keep the interface similar to the cli, it should be something like:

async fn request_redemption(
		&self,
		redeem_address: EthereumAddress,
		exact_amount: Option<NumberOrHex>,
		executor_address: Option<EthereumAddress>,
	) -> Result<Hash, AnyhowRpcError>;

This way the query is { redeem_address: "0xabab.." } for a max redeem, and { redeem_address: "0xabab..", exact_amount: "0xb1ab1a.." } for an exact redeem, which is closer to the cli convention of redeem vs redeem --exact 1234.

With the current solution we're introducing a new convention of amount: "Max".

FWIW I don't think the latter is a bad idea necessarily (it's more explicit than assuming max by default) but it should be a conscious decision, and then we should plan to update the CLI too to make things consistent.