Fix for excess propose signals.

[Frozen]

Added block number for ReadySignal. Additional check for firing block proposing from setupForNewConsensus.

Main idea here is that we check if next key is not my - do not trigger propose.
https://github.com/harmony-one/harmony/pull/4816/files#diff-255a5cdd5516e7293e60a47a92503360676ddffb7e48e505598a589753b568c2R612

[sophoah]

why re-creating a new function and not use directly IsLeaderRotationInternalValidators ?

[Frozen]

i don't need to know which kind of rotation, i need the fact.

[sophoah]

ok and why recreating the function ?

[Frozen]

because leader rotation does not affect blockchain anyhow. It means, that we can safely remove internal and external epochs, and left only v2. Exactly in this part of code, i don't need to know which kind of rotation we use, i need to know that we have it active.

[sophoah]

@Frozen please fix travis CI:

# github.com/harmony-one/harmony/consensus [github.com/harmony-one/harmony/consensus.test]
consensus/consensus_test.go:100:27: too many arguments in call to consensus.finalCommit
	have (number, number, bool)
	want (bool)

[Frozen]

fixed, lost some code during rebase

[mur-me]

Checked against localnet via make debug-ext.

Faced both pre and post leaderRotationconsensus epochs in the !consensus.isRotation(blk.Epoch()) condition

[Frozen]

This fixes certain issues, additional fixes will be in the next Prs.