Use `truncateBytes` to log `blockRoot`

[nazarhussain]

I'd like blockRoot to be fully printed consistently so that it's easier to debug you search for it through explorer then copy it to our loki explorer. If it's not consistent then it make it harder to debug. Does anybody agree?

this is different to peerId where we print it fully 1 time and pretty print in all other times

Originally posted by @twoeths in https://github.com/ChainSafe/lodestar/pull/8390#pullrequestreview-3222743320

[twoeths]

it would also be nice to log get consensus on root blockRoot vs blockRootHex vs rootHex log

[nflaig]

it would also be nice to log get consensus on root blockRoot vs blockRootHex vs rootHex log

Either root or blockRoot, adding Hex suffix in the log context doens't make sense, although it's useful for variable names, but that's different.

When it comes to root vs. blockRoot I feel like it depens on the context of the log, if it's clearly talking about a block, then just root might be fine.

If we wanna keep it simple, just use blockRoot all the time.