demote log level for TIMESTAMP_TOO_FAR_IN_FUTURE errors

[arvidn]

Purpose:

This patch aims to match the log level with the attention needed from the user.

Current Behavior:

When a node receives an unfinished block with a timestamp that's more than 2 minutes ahead of its own clock, it's rejected with a ConsensusError exception, printing a very serious looking error to the log. We expect to receive more of these invalid blocks while transitioning to more 1.8 full nodes.

Prior to version 1.8.0 the upper timestamp limit was 5 minutes, now it's 2. This means that a sizeable part of the network still forwards blocks more than 2 minutes ahead of wall-clock.

New Behavior:

Instead of printing the stack trace at ERROR log level, print a message at INFO log level describing the validation failure.

Testing Notes:

I'm running this locally and have two instances printed to my log so far:

2023-08-17T22:09:41.847 full_node full_node_server        : INFO     Received block with timestamp too far into the future
2023-08-17T23:11:12.479 full_node full_node_server        : INFO     Received block with timestamp too far into the future

[danieljperry]

Agreed with changing the severity of this message to INFO.

[github-actions]

File	Coverage	Missing Lines
chia/full_node/full_node.py	50.0%	lines 1648-1649, 1831
chia/server/ws_connection.py	60.0%	lines 415, 442
chia/util/errors.py	60.0%	lines 200-201

Total	Missing	Coverage
16 lines	7 lines	56%

[emlowe]

Approved with coverage diff exception