Log detailed timing of block creation steps

[fab-10]

PR description

if log level is at debug, detailed timing of block creation steps are logged, along with the standard block info.

Log will look like this:

2024-04-05 10:54:46.962+00:00 | MinerExecutor | INFO  | BlockMiner | Produced #260,775 / 63 tx / 0 om / 1,577,124 (2.6%) gas / (0xb6907722d13c36fb54747d11f4b7c734d6b57035ca1a3428e4b5c9f347644b63) in 0.000s, timing [Started at 2024-04-05T10:54:46.693633274Z, protocolWait=254ms, duplicateWorldState=0ms, preTxsSelection=3ms, txsSelection=9ms, blockAssembled=1ms, importingBlock=0ms, notifyListeners=0ms, log=0ms]

Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests

[macfarla]

@fab-10 what does the PT signify before the number eg protocolWait=PT0.199224809S,

also is S for seconds? I think lower case s is easier to read with numbers

[fab-10]

@fab-10 what does the PT signify before the number eg protocolWait=PT0.199224809S,

also is S for seconds? I think lower case s is easier to read with numbers

just using the default Duration.toString() but I agree that for so short duration could not be very readable, will propose another format, that works with millis

[fab-10]

@macfarla updated to look like this one:

protocolWait=254ms, duplicateWorldState=0ms, preTxsSelection=3ms, txsSelection=9ms, blockAssembled=1ms