Reduce Log Level For Leader Behind Follower Case

[gabriel-aranha-cw]

Reducing the Log Level from ERROR to WARN for the Leader is Behind follower message. As it is now, the current implementation makes the follower nodes pull the blocks from Substrate instead of the Leader node. This will log the message very frequently and will only be reduced in a future enhancement when the follower nodes start receiving the entries from the leader node directly.

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review [1-5]	1
🧪 Relevant tests	No
🔒 Security concerns	No
⚡ Key issues to review	None

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Convert the log message to use structured logging Consider using structured logging for better traceability and filtering. Instead of formatting the log message directly, use key-value pairs to log the data. src/eth/consensus/mod.rs [778-781] tracing::warn!( - "leader is behind follower: arrived_block: {}, header_block: {}", - last_last_arrived_block_number, - header.number + "leader is behind follower", + arrived_block = last_last_arrived_block_number, + header_block = header.number +); Suggestion importance[1-10]: 9 Why: The suggestion to use structured logging improves traceability and filtering, which is a best practice for logging. This change enhances the maintainability and readability of the log messages.	9