Use libp2p in catalyst

[Xela101]

New Pull Request Submissions:

1. Have you followed the guidelines in our Contributing document?
2. Have you checked to ensure there aren't other open Pull Requests for the same update/change?
3. I have added tests to cover my changes.
4. All new and existing tests passed.
5. Have you lint your code locally prior to submission?
6. Does your code follows the code style of this project?
7. Does your change require a change to the documentation.
   • I have updated the documentation accordingly.
8. Have you added an explanation of what your changes do and why you'd like us to include them?
9. Have you inserted a keyword and link to the issues the PR closes in its descriptions (ex closes #1) ?
10. Is you branch up to date, have you integrated all the latest changes from develop and resolved conflicts ?

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  Bug fix,
  Feature

• What is the current behavior?

Nodes use PeerId's while LibP2P uses MultiAddress's, because we are integrating LibP2P within Catalyst there is no point in needing to maintain both. However.. we could use a more compressed format of MultiAddress over protobuf messages and reconstruct to a multi-address for a smaller message payload. #1270

From discussions at the start of the year our RPC library is being deprecated in favor of using the Etherium Api endpoints and DFS api. What should we do with the current RPC projects. #1271

MessageDto is used heavily by dotnetty, this can probably be remove now as well as the channel context in observers. #1272

New LibP2P handlers should be added via AutoFac DI. #1273

Use the plain generic IPeerClient, IPeerService libraries for generic services instead of the one specific for libp2p.

• What is the new behavior (if this is a feature change)?
  LibP2P is used for the networking layer

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

• Other information:
  closes Use libp2p in catalyst #1245 Add unit tests to custom Catalyst LibP2P protocol #1261 Allow node to discover nodes before the sync process starts. #1262 Increase sync download range message size limit. #1260 Use only connected peer nodes for sync progress. #1259 Fix issue with limitation on message size #1258 Add variant length to protobuf wire messages over custom Catalyst LibP2P protocol #1257 Use DFS Peer Discovery in Catalyst #1247 Convert to TCP from UDP #909 Current LibP2P implementation doesn't support message from one peer to another, only swam messaging. #1250 Use MultiFormat's multi address in places instead of IP/Port/PublicKey #1249 Create new pipeline handlers for PubSub messages. #1251 Connect PeerRepository to DFS for the population of new nodes and retrieval of seed nodes. #1248 As DFS service I want to use catalyst peer discovery DB #1144

[sudhirtibrewal]

looks ok. need through testing

[franssl]

Changes look good to me!