Redefine P2P communication and message formats after using lisk-codec

[ishantiw]

Description

Update the content of each endpoints to

getPeers

{
  peers: {
     ipAddress: string;
     port: uint32;
  }[]
}

getNodeInfo

{
  advertiseAddress: boolean;
  networkID: string;
  protocolVersion: string;
  nonce: string;
  // custom field injected from outside
  options: {
    height: uint32;
    maxHeightPrevoted: uint32;
    blockVersion: uint32;
  },
}

updateNodeInfo

// Only accept custom field
{
  height: uint32;
  maxHeightPrevoted: uint32;
  blockVersion: uint32;
}

Handshake

It should only require below information

{
  advertiseAddress: boolean;
  port: uint32;
  networkId: string;
  protocolVersion: string;
  nonce: string;
}

Expected behavior

• P2P layer should communicate messages en/decoded using lisk-codec
• Should allow custom fields for custom modules by accepting schema from the user - Solved in Allow custom schema in P2P constructor - Partially Closes #5419 #5434

Actual behavior

• Some messages are not well defined for p2p communicated and we need to finalize which fields will be required in the schema for encoding.

Steps to reproduce

N/A

Which version(s) does this affect? (Environment, OS, etc...)

5.0