feat: miner: log detailed timing breakdown when mining takes longer than the block's timestamp

[arajasek]

Related Issues

We're looking into reports of missed blocks due to mining taking too long. It's currently hard to analyze what the cause might be, because we only log the detailed breakdown of timing if the entire process was longer than 30s. However, we also want this information if by the time we're done producing the block, we've already reached the block's timestamp

Proposed Changes

Log the detailed breakdown more liberally

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[fridrik01]

LGTM