Coordinator - shall not log error when it recovers from failure

[jpnovais]

Remenber not to put too much unhelpful information or too little important information, be specific.

Impact

Impact: All environments

Describe the bug

Steps to Reproduce

Coordinator logs an error when Shomei (Linea zk State Manager) is out of sync, saying that conflation failed.
However coordinator seems to be resilient to this failure, therefore this log shall be logged as INFO only instead

time=2025-01-13T17:17:18,399Z level=ERROR message=Traces conflation failed: batch=[14543211..14543228]18 errorMessage=net.consensys.linea.jsonrpc.JsonRpcErrorResponseException: code=-32602 message=BLOCK_MISSING_IN_CHAIN - block 14543211 is missing errorData=null | logger=ProofGeneratingConflationHandlerImpl thread=vert.x-eventloop-thread-4 | java.util.concurrent.CompletionException: net.consensys.linea.jsonrpc.JsonRpcErrorResponseException: code=-32602 message=BLOCK_MISSING_IN_CHAIN - block 14543211 is missing errorData=null\n	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)\n	at 

Steps to reproduce the bug:

Not sure how to reproduce exactly, but maybe adding an extra Shomei instance that cannot to Besu to get the try logs and is deliberately out of sync.