fastsync: update the metrics during fast-sync

[JayT106]

Closes #3507

[tac0turtle]

I think this is fine for now, Im not the biggest fan of passing the consensus state as we are doing.

This made me think that there may be some metrics that other reactors may want to touch, does it make sense to have node pkg metrics that various reactors can update depending on the various states of a node?

[codecov]

Codecov Report

Merging #6590 (8ef165a) into master (6e238b5) will increase coverage by 0.02%.
The diff coverage is 37.50%.

❗ Current head 8ef165a differs from pull request most recent head 9517ea8. Consider uploading reports for the commit 9517ea8 to get more accurate results

@@            Coverage Diff             @@
##           master    #6590      +/-   ##
==========================================
+ Coverage   61.04%   61.07%   +0.02%     
==========================================
  Files         295      295              
  Lines       27968    27956      -12     
==========================================
  Hits        17074    17074              
+ Misses       9166     9157       -9     
+ Partials     1728     1725       -3     

Impacted Files	Coverage Δ
internal/blockchain/v0/reactor.go	63.92% <0.00%> (-1.30%)	⬇️
internal/consensus/reactor.go	68.04% <0.00%> (+0.97%)	⬆️
internal/consensus/state.go	67.30% <60.00%> (-0.07%)	⬇️
internal/consensus/peer_state.go	78.94% <0.00%> (-1.76%)	⬇️
internal/p2p/transport_memory.go	84.21% <0.00%> (-1.32%)	⬇️
abci/client/socket_client.go	38.54% <0.00%> (-1.15%)	⬇️
internal/p2p/switch.go	60.18% <0.00%> (-0.47%)	⬇️
internal/p2p/router.go	81.58% <0.00%> (-0.24%)	⬇️
internal/statesync/reactor.go	58.71% <0.00%> (-0.16%)	⬇️
... and 12 more