Channel Resolution Reconstruction

Nobody has claimed this yet.

The on chain transactions required to fully resolve a channel on chain will be persisted by lightningnetwork/lnd/4157. However, this data will only be present for channels that are closed after the node upgrades to a version of lnd running this change. This leaves many projects without tools to accurately account for previously closed channels.

Given a channel ID, examine the closing transaction (and subsequent transactions) on chain to determine the resolutions that occurred on chain. This will require a connection to a node with `--txindex` enabled.

- Optionally allow faraday to connect directly to a node ()
- Add ChannelResolutions endpoint which optimistically queries lnd
- If no resolutions are persisted, and Faraday is connected to a node, get resolutions from chain
- For first iteration, keep resolutions in memory; consider persisting further on

Start by mapping Faraday’s existing channel-resolution lookup and API entry points; the issue names no files or tests. Review the lnd persisted-resolution behavior and the requirements for querying a node with --txindex, including closing and subsequent transactions. Done means a ChannelResolutions endpoint can fall back to reconstructed on-chain resolutions and keep first-iteration results in memory.

Written by the indexing model from the issue text.