Adding lighthouse/peers methods in BeaconNodeHttpClient

[leruaa]

Issue Addressed

Issue #3041

Proposed Changes

• Add the corresponding get_lighthouse_peers() and get_lighthouse_connected_peers() methods to BeaconNodeHttpClient
• Impl Deserialize on Peer struct and all fields structs recursively

[CLAassistant]

All committers have signed the CLA.

[leruaa]

I noticed that the score is not serialized as:

"score": {
  "score": 0
}

like described in the book, but like that:

"score": {
  "RealScore": {
    "lighthouse_score": 0,
    "gossipsub_score": 0,
    "ignore_negative_gossipsub_score": false,
    "score": 0
  }
}

Do we want to keep all the score details? Maybe we could streamline to just:

"score": 0

But obviously, that another breaking change...

[michaelsproul]

I think we need to avoid erroring in this case, or it'll create issues when translating Instants between machines. If the duration we get off the wire is greater than our current instant then it'll error. Ideally we could use saturating_sub, but it doesn't exist for Instant, so I think our best option is probably to do .checked_sub(duration).unwrap_or_else(Instant::now).

[dapplion]

Un-addressed comment by author @leruaa. Double checking there's still demand to call lighthouse only APIs programatically with the internal eth2 tooling?

[michaelsproul]

I think we can close this, as Jack has implemented it more recently in #4937

[dapplion]

Superseded by

• Add client support for the lighthouse/peers route #4937