Fix incorrect error logged when a newly imported block has an invalid payload

[ajsutton]

PR Description

When a block with an invalid payload was imported while the EL was in sync, Teku failed to find the latestValidHash because it wasn't checking the direct parent in this case (the code was originally only dealing with blocks that were imported optimistically and then later found to be invalid).

Teku's behaviour was correct (and there was even a test for it) but in incorrectly logged:

2022-07-21 10:53:00.508 ERROR - Could not find latest valid execution payload hash (0xfa87aa1b3ee36c763fb5b083aa3fed49fd037371ffc4949b03f894fcf5c3c099) in the non-finalized chain. Optimistic sync may have finalized an invalid transition block.

Now it does not.

Documentation

• I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

• I thought about adding a changelog entry, and added one if I deemed necessary.

[rolfyone]

LGTM