Error on handling HoneyBadger message.

[SurfingNerd]

we do have a lot of HoneyBadger message that can not be handled.

One known origin for this message is a missmatch between the HBBFT Signing key and the Transaction Signing Key as we have in the protocol here: #62
IN this case block production did not work anymore, because 1 out of 2 Nodes missed out, so we did not get the 2/3 majority.

But there might be other cases that need get attention.

[SurfingNerd]

2022-03-04 04:47:02 Worker Hbbft1 INFO engine public master key: PublicKey(0753..fd38)
2022-03-04 04:47:02 Worker Client3 ERROR consensus Error on handling HoneyBadger message from NodeId(0xb8cf…9d4a) in epoch 124265 error: UnknownSender
2022-03-04 04:47:02 Worker Client0 ERROR consensus Error on handling HoneyBadger message from NodeId(0xb8cf…9d4a) in epoch 124265 error: UnknownSender
2022-03-04 04:47:02 Worker Client0 INFO import 36/50 peers 3 MiB chain 0 bytes queue RPC: 0 conn, 1 req/s, 12 µs2022-03-04 04:47:02 Worker Client1 ERROR consensus Error on handling HoneyBadger message from NodeId(0xb8cf…9d4a) in epoch 124265 error: UnknownSender

2022-03-04 04:47:02 Worker Client0 ERROR consensus Error on handling HoneyBadger message from NodeId(0xb8cf…9d4a) in epoch 124265 error: UnknownSender
2022-03-04 04:47:17 Worker Client3 WARN sync No session exists for peerId 29
2022-03-04 04:47:34 Worker Client3 INFO import 36/50 peers 3 MiB chain 0 bytes queue RPC: 0 conn, 0 req/s, 12 µs

[SurfingNerd]

it happens if a node drops out of current honey badger set, on the next block the node is not known to the honey badger engine, and cannot handle messages from the past. This is very common

[SurfingNerd]

happened again on performance testnet.
022-08-29 23:41:08 Error on handling HoneyBadger message from NodeId(0xfd4a…ec02) in epoch 18127 error: UnknownSender

It hbbft27 for this example