Don't ban nodes for block created in early catchup

[georgeee]

Problem: when a node is in early catchup and creates a block, it might be considered worse than root and the node to be banned for gossiping it.

This is especially easy to reproduce in a network with a few large-stake BPs, but may happen in network like mainnet too, with a lower probability.

Discussion of the problem: https://www.notion.so/minaprotocol/Banning-of-recently-bootstrapped-block-producer-dd98f2268c9e4a6eb4cbd7730d3a2865

Solution: if parent of the transition is in root history, do not ban.

Additionally, if we've seen gossip with the parent of transition and its ancestor was in root history, do not ban. This one is implemented heuristically via an LRU cache.

Explain how you tested your changes:

• Tested on a private cluster

Checklist:

• Dependency versions are unchanged
  • Notify Velocity team if dependencies must change in CI
• Modified the current draft of release notes with details on what is completed or incomplete within this project
• Document code purpose, how to use it
  • Mention expected invariants, implicit constraints
• Tests were added for the new behavior
  • Document test purpose, significance of failures
  • Test names should reflect their purpose
• All tests pass (CI will check this if you didn't)
• Serialized types are in stable-versioned modules
• Does this close issues? None

[georgeee]

!ci-build-me

[georgeee]

!ci-build-me

[georgeee]

!ci-build-me

[deepthiskumar]

!approved-for-mainnet