Show both client config and local config bitcoin nodes in guardian UI

[wbobeirne]

This is a common point of confusion, there are 2 bitcoin nodes that get configured but we only show one of them. We should probably show both, and distinguish which is which.

Somewhat related is fedimint/fedimint#3531 for configuring both.

[elsirion]

For context: one is used for consensus, this is typically a local bitcoind, while the other is given to clients to fetch the deposit status of their transactions from. That one is typically an esplora instance rn because we don't support electrum for that (incompatible merkle proof formats that I never got around to converting into each other fedimint/fedimint#4223) and bitcoind isn't really built for being a public API service.

[Kodylow]

Note: local config isn't even exposed to the admin UI, needs a new api endpoint to expose it. In the meantime if this is just the client info it probably shouldn't even be exposed at all in the gaurdian UI