Node connection port mis-configuration issue for raft consensus

[fixanoid]

Its possible to mis-configure Quorum running in raft mode in such a way that raft connection is established, but eth.dev.P2P is not. This results in all kinds of weirdness including blocks getting propagated, but txns from followers are not. In console, admin.peers list is empty, tho raft election occurs and is logged correctly in the log files.

Tested using quorum-examples. To repeat, initialize vagrant quorum-examples, edit permissioned-nodes.json to match below content and run raft-init followed by raft-start. In the example all ports following the IP address are wrong.

[
  "enode://ac6b1096ca56b9f6d004b779ae3728bf83f8e22453404cc3cef16a3d9b96608bc67c4b30db88e0a5a6c6390213f7acbe1153ff6d23ce57380104288ae19373ef@127.0.0.1:22000?discport=0&raftport=50401",
  "enode://eacaa74c4b0e7a9e12d2fe5fee6595eda841d6d992c35dbbcc50fcee4aa86dfbbdeff7dc7e72c2305d5a62257f82737a8cffc80474c15c611c037f52db1a3a7b@127.0.0.1:22225?discport=0&raftport=50406",
  "enode://239c1f044a2b03b6c4713109af036b775c5418fe4ca63b04b1ce00124af00ddab7cc088fc46020cdc783b6207efe624551be4c06a994993d8d70f684688fb7cf@127.0.0.1:22222?discport=0&raftport=50407"
]

[fixanoid]

In the interim, a new method in raft has been provided to compare the state of raft cluster and connected peers. Use raft.cluster to list the content of raft peer connectivity and use admin.peers to compare that the right peers have connected.