Add "starting" info logging in the various components that have non-trivial startup cost

[rvagg]

On larger nodes, particularly archival nodes, the Lotus startup time is very expensive. Logging out of badger suggests that it gets done with loading its indexes relatively fast but then there's a significant wait until the node is ready. e.g. we know that FEVM archival nodes take at least 30 minutes to properly start up. This is less pronounced but still noticeable on splitstore nodes.

For the purpose of diagnosing and for helping users understand what's going on, it would be helpful to info-log the start process of the various modules that do more than just instantiate. Various modules have startup procedures that they need to undertake before they are "ready", so we should log the start and the ready times of these.

This might be a matter of walking through node/builder_chain.go and looking at each of the modules and considering whether more logging should be added to them or not.

[rjan90]

How much overlap is it between this issue ticket, and the one written up here: #12568 ?

[rvagg]

Not really any overlap, this one asks for logging so we can see what's going on. I suspect once we start this we find out that most of it is not useful information so they should be debug-level but there are some modules that are quite heavy for which info-level would be helpful.