spring 1.0 adds redundant information in log output during replay

[spoonincode]

Prior to spring 1.0 during replay the logs look like,

info  2024-11-07T18:29:33.633 nodeos.50 controller.cpp:528            replay               ] 500 of 402483191
info  2024-11-07T18:29:34.704 nodeos.50 controller.cpp:528            replay               ] 1000 of 402483191
info  2024-11-07T18:29:35.463 nodeos.50 controller.cpp:528            replay               ] 1500 of 402483191
info  2024-11-07T18:29:36.175 nodeos.50 controller.cpp:528            replay               ] 2000 of 402483191
info  2024-11-07T18:29:36.899 nodeos.50 controller.cpp:528            replay               ] 2500 of 402483191
info  2024-11-07T18:29:37.638 nodeos.50 controller.cpp:528            replay               ] 3000 of 402483191

As of spring 1.0 the logs look like

info  2024-11-07T18:28:34.018 nodeos.s1 controller.cpp:1670           replay_block_log     ] 500 of 402483191
info  2024-11-07T18:28:35.024 nodeos.s1 controller.cpp:3637           log_applied          ] Received block ddc03486114e6a1c... #1000 @ 2018-06-09T12:06:33.000 signed by eosio [trxs: 1, lib: 999, net: 10384, cpu: 100495 us, elapsed: 1858 us, applying time: 2049 us, latency: 202458122024 ms]
info  2024-11-07T18:28:35.024 nodeos.s1 controller.cpp:1670           replay_block_log     ] 1000 of 402483191
info  2024-11-07T18:28:35.720 nodeos.s1 controller.cpp:1670           replay_block_log     ] 1500 of 402483191
info  2024-11-07T18:28:36.423 nodeos.s1 controller.cpp:3637           log_applied          ] Received block 206e680a75958c81... #2000 @ 2018-06-09T12:14:53.000 signed by eosio [trxs: 1, lib: 1999, net: 10384, cpu: 99964 us, elapsed: 1958 us, applying time: 2507 us, latency: 202457623423 ms]
info  2024-11-07T18:28:36.423 nodeos.s1 controller.cpp:1670           replay_block_log     ] 2000 of 402483191
info  2024-11-07T18:28:37.134 nodeos.s1 controller.cpp:1670           replay_block_log     ] 2500 of 402483191
info  2024-11-07T18:28:37.850 nodeos.s1 controller.cpp:3637           log_applied          ] Received block 3755ae4c7e9c5751... #3000 @ 2018-06-09T12:23:13.500 signed by eosio [trxs: 1, lib: 2999, net: 10384, cpu: 106037 us, elapsed: 1974 us, applying time: 2162 us, latency: 202457124350 ms]
info  2024-11-07T18:28:37.850 nodeos.s1 controller.cpp:1670           replay_block_log     ] 3000 of 402483191
info  2024-11-07T18:28:38.551 nodeos.s1 controller.cpp:1670           replay_block_log     ] 3500 of 402483191
info  2024-11-07T18:28:39.254 nodeos.s1 controller.cpp:3637           log_applied          ] Received block b7540f01a5ff33f0... #4000 @ 2018-06-09T12:31:34.500 signed by eosio [trxs: 0, lib: 3999, net: 0, cpu: 100 us, elapsed: 20 us, applying time: 39 us, latency: 202456624754 ms]
info  2024-11-07T18:28:39.254 nodeos.s1 controller.cpp:1670           replay_block_log     ] 4000 of 402483191
info  2024-11-07T18:28:39.962 nodeos.s1 controller.cpp:1670           replay_block_log     ] 4500 of 402483191

If we're going to log log_applied during the replay maybe don't log the replay_block_log too (though this will be a very different log output compared to how it has been since eosio 1.0!)

[bhazzard]

Decision to remove log_applied.