Contradictory logs when syncing

[nalepae]

Describe the bug

When syncing, it's possible to have these 2 contradictory logs at the same time:

• Execution client is not syncing
• Beacon node is not respecting the follow distance. EL client is syncing.

[2024-04-29 13:25:37]  INFO blockchain: Called fork choice updated with optimistic block finalizedPayloadBlockHash=0x8e59bee88968 headPayloadBlockHash=0xb41495b2e9c7 headSlot=1540628
[2024-04-29 13:25:37]  INFO blockchain: Synced new block block=0x78005f07... epoch=48144 finalizedEpoch=48142 finalizedRoot=0x1bcc7756... slot=1540628
[2024-04-29 13:25:37]  INFO blockchain: Finished applying state transition attestations=128 kzgCommitmentCount=3 payloadHash=0xb41495b2e9c7 slot=1540628 syncBitsCount=488 txCount=107
[2024-04-29 13:25:46]  INFO p2p: Connected peers inboundTCP=0 outboundTCP=72 total=72
[2024-04-29 13:25:49]  WARN execution: Execution client is not syncing
[2024-04-29 13:25:49] ERROR execution: Beacon node is not respecting the follow distance. EL client is syncing. lastBlockNumber=0
[2024-04-29 13:25:51]  INFO blockchain: Called new payload with optimistic block payloadBlockHash=0x3ec668adf90d slot=1540629
[2024-04-29 13:25:51]  INFO blockchain: Called fork choice updated with optimistic block finalizedPayloadBlockHash=0x8e59bee88968 headPayloadBlockHash=0x3ec668adf90d headSlot=1540629
[2024-04-29 13:25:51]  INFO blockchain: Synced new block block=0x9f9a161d... epoch=48144 finalizedEpoch=48142 finalizedRoot=0x1bcc7756... slot=1540629
[2024-04-29 13:25:51]  INFO blockchain: Finished applying state transition attestations=128 payloadHash=0x3ec668adf90d slot=1540629 syncBitsCount=488 txCount=5