Integrate Yamux substreams into the light client logic

[StoyanDrumev]

• /kad - Allows the client to respond to FIND_NODE Kademlia requests

• /light/2

  Light clients are applications that fetch the required data that they need from a Polkadot node with an associated proof to validate the data. The light client messages make this functionality possible

  • Create RemoteCallRequest, RemoteReadRequest, RemoteReadChildRequest messages that have to Protobuf encoded
  • Validate RemoteCallResponse and RemoteReadResponse messages that are Protobuf encoded

• /sync/warp

  Warp sync is the fastest available process designed specifically for light clients’ needs.

  • [Implement grandpa justifications verification algorithm](https://spec.polkadot.network/#warp-sync) using the info coming from /sync/warp
  • Implement a sync query process based on this [algorithm](https://spec.polkadot.network/#algo-light-clients-query-state) because it’s used by the warp sync algorithm
  • Persist latest finalized block information to DB

[vikinatora]

Keep in mind this issue when doing the warp sync logic. smol-dot/smoldot#239 and this PR smol-dot/smoldot#441

[vikinatora]

Not sure if relevant for this issue but see this issue qdrvm/kagome#1534 and chat in element https://matrix.to/#/!oZltgdfyakVMtEAWCI:web3.foundation/$Q7yh3B9vCDDWnMyhLqr_lzt7oZbI4_Kvogxd8EvRGO8?via=web3.foundation&via=matrix.org&via=matrix.parity.io

[vikinatora]

@StoyanDrumev This task can be divided into 4 smaller tasks, one for each endpoint:

1. /kad - Task name could be 'Add kademlia protocol negotiation logic' - The task is completed already
2. /light/2 - Task name could be 'Add light messages protocol negotiation and request handling logic'
3. /sync/warp - Task name could be 'Add warp sync messages protocol negotiation and request handling logic'

and 4th task regarding the subtasks for /sync/warp:

[Implement grandpa justifications verification algorithm](https://spec.polkadot.network/#warp-sync) using the info coming from /sync/warp
Implement a sync query process based on this [algorithm](https://spec.polkadot.network/#algo-light-clients-query-state) because it’s used by the warp sync algorithm
Persist latest finalized block information to DB

It should a separate task called 'Implement light client sync algorithm' with description the text above.

[StoyanDrumev]

• [Add kademlia protocol negotiation logic ] Add kademlia protocol negotiation logic #61
• [Add light messages protocol negotiation and request handling logic ] Add light messages protocol negotiation and request handling logic #62
• [Add warp sync messages protocol negotiation and request handling logic] Add warp sync messages protocol negotiation and request handling logic #63
• [Implement light client sync algorithm ]Implement light client sync algorithm #64