EVM: Kernel: store receipt and object once transaction is computed

Context

Contributes to #5873 (closed)

The transaction objects and receipts are stored at the end of the execution of a block. To simplify reboot scheduling, it would be easier to store them as soon as a transaction is treated, otherwise all the information need to stored, then reloaded during next reboot.

The proposal here is to store receipts and objects as soon as the transaction is created. A container is added to keep track of the values used during block production. This container is enough to produce the receipt and object.

This doesn't include the reboot scheduling, to be done as a follow up.

Follow up: !9214 (merged)

Manually testing the MR

It's a refacto, and changes no logic, so current tests should be enough.

Checklist

• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR