EVM/Node: Add block info in `blueprint_applied` event

What

Add more information in the blueprint_applied event.

Why

Help with monitoring. At the moment the most informative event is the one repeating the kernel log, but with the new runtime, this event is not sent anymore.

How

Add the desired information in the node event.

Manually testing the MR

Run a sandbox, create a block, and look at the output

Oct 23 16:14:29.368: Storing block 7 at 2024-10-23T14:14:29Z containing 0 transaction(s) for 0 gas used.
Oct 23 16:14:29.374: Applied a blueprint for level 7 at 2024-10-23T14:14:29Z containing 0
Oct 23 16:14:29.374:   transactions for 0 gas leading to creating block
Oct 23 16:14:29.374:   0xed681f7a5d5cf62016349eeb9472d895526aa5cccb683c1c610f621de[...].

and at the daily logs

2024-10-23T14:14:29.374-00:00 [evm_node.dev.blueprint_application] Applied a blueprint for level 7 at 2024-10-23T14:14:29Z containing 0 transactions for 0 gas leading to creating block 0xed681f7a5d5cf62016349eeb9472d895526aa5cccb683c1c610f621de[...].

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR