Gloas beacon block validation update

[ahshum]

No description provided.

[ahshum]

According to

nimbus-eth2/beacon_chain/gossip_processing/gossip_validation.nim

Lines 929 to 934 in b2276f6

	# Implementation restrictions:
	#
	# - We don't know if the parent state had execution enabled.
	# If it had, and the block doesn't have it enabled anymore,
	# we end up in the pre-Merge path below (`else`) and REJECT.
	# Such a block is clearly invalid, though, without asking the EL.

It seems that we need some sort of refactoring for this?

[ahshum]

nimbus-eth2/beacon_chain/gossip_processing/gossip_validation.nim

Lines 362 to 367 in b2276f6

	# The condition:
	# [REJECT] The block's parent (defined by `block.parent_root`) passes all
	# validation (excluding execution node verification of the
	# `block.body.execution_payload`).
	# cannot occur here, because Nimbus's optimistic sync waits for either
	# `ACCEPTED` or `SYNCING` from the EL to get this far.

[github-actions]

Unit Test Results

       15 files  ±0    3 030 suites  ±0   1h 29m 22s ⏱️ +14s
12 067 tests ±0  11 497 ✔️ ±0  570 💤 ±0  0 ❌ ±0 
76 511 runs  ±0  75 659 ✔️ ±0  852 💤 ±0  0 ❌ ±0 

Results for commit 1a9ec88. ± Comparison against base commit 0ae66b3.

♻️ This comment has been updated with latest results.