Fix Goerli transition issue

[LukaszRozmej]

Changes:

• NewPayloadV1Handler ShouldProcessBlock method was introduced. This decides if block should be processed and with what ProcessingOptions flags it will be processed. For reorging terminal blocks it removes IgnoreParentNotOnMainChain flag. This is main fix for Goerli transition issue. We are also waiting for the hive tests to get more sophisticated in order to be able to catch this issues in them.
• BlockchainProcessor to return full block on InvalidBlock exception and event.
• BlockTreeLookupOptions.AllowInvalid to also look into (latest) invalid blocks.
• BlockTree will keep full recent invalid blocks instead of just hashes.
• InvalidChainTracker to use invalid block parent directly rather than doing lookup.
• InvalidChainTracker will use BlockTreeLookupOptions.AllowInvalid | BlockTreeLookupOptions.TotalDifficultyNotNeeded BlockTreeLookupOptions.DoNotCalculateTotalDifficulty options when looking up a block header.
• Hookup InvalidChainTracker SetupBlockchainProcessorInterceptor in EngineModuleTests.
• Added EnumExtensions.AllValuesCombinations (for testing purposes).

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Other (please describe):

Testing

Requires testing

• Yes
• No

In case you checked yes, did you write tests??

• Yes
• No

[asdacap]

LGTM

[LukaszRozmej]

Looks like 1 test regression in transition, 2 tests failing on standard, but they failed before.
https://github.com/NethermindEth/nethermind/actions/runs/2846761961
https://github.com/NethermindEth/nethermind/actions/runs/2846761591

[MarekM25]

Code looks fine. Could you explain why we changed invalid blocks handling? Did we fix some hive tests scenario?

Before we merge it I wanted to be sure that we didn't introduce any hive regression and we confirm fix with Mario's new tests