Lot's of warning message when starting a fresh local chain now

[maoueh]

Two places needed to be adjusted:

• nodeos/snapshot.go complains it cannot find snapshot in warning, but it's a fresh chain. Message is in warning and it's misleading because we talk about a replay, which it not the case here. I suggest we move that to INFO and improve the message
• Now that nodeos maps it's warning to zap level, it's annoying to have them by default. We should probably try to tweak it to have ERROR only. That might prove harder than it seems because the level is at the app level while we would need to tweak it for a particular package here.

Note also that I was not able to choose a label for this issue, no label seems to fit here, where is the enhancement like label?

$ ./dfuseeos start
Starting dfuse for EOSIO with config file './dfuse.yaml'
Launching applications: abicodec,apiproxy,blockmeta,dashboard,dgraphql,eosq,eosws,fluxdb,merger,mindreader,node-manager,relayer,search-archive,search-indexer,search-live,search-router,trxdb-loader
Your instance should be ready in a few seconds, here some relevant links:

  Dashboard:        http://localhost:8081

  Explorer & APIs:  http://localhost:8080
  GraphiQL:         http://localhost:8080/graphiql

Cannot find latest snapshot, will replay from blocks.log (nodeos/snapshot.go:153)
warn  2020-05-08T21:58:27.837 thread-0  platform_timer_accurac:64     compute_and_print_ti ] Checktime timer accuracy on this platform and hardware combination is poor; accuracy of subjective transaction deadline enforcement will suffer (log_plugin/to_zap_log_plugin.go:53)
warn  2020-05-08T21:58:27.856 thread-0  controller.cpp:583            startup              ] No existing chain state or fork database. Initializing fresh blockchain state and resetting fork database (log_plugin/to_zap_log_plugin.go:53)
warn  2020-05-08T21:58:27.857 thread-0  controller.cpp:452            initialize_blockchai ] Initializing new blockchain with genesis state (log_plugin/to_zap_log_plugin.go:53)
Cannot find latest snapshot, will replay from blocks.log (nodeos/snapshot.go:153)
warn  2020-05-08T21:58:28.699 thread-0  platform_timer_accurac:64     compute_and_print_ti ] Checktime timer accuracy on this platform and hardware combination is poor; accuracy of subjective transaction deadline enforcement will suffer (log_plugin/to_zap_log_plugin.go:53)
warn  2020-05-08T21:58:28.706 thread-0  controller.cpp:583            startup              ] No existing chain state or fork database. Initializing fresh blockchain state and resetting fork database (log_plugin/to_zap_log_plugin.go:53)
warn  2020-05-08T21:58:28.706 thread-0  controller.cpp:452            initialize_blockchai ] Initializing new blockchain with genesis state (log_plugin/to_zap_log_plugin.go:53)

[sduchesneau]

I fixed #1 (replay...) For #2, I don,t think we should do this now. let's keep levels aligned. pushing to a new "improvement" issue