Kernel/Evm: track bip ticks per run/per block

What

Ensure that ticks, as injected into the gas price backlog are correctly counted once, and only once.

Why

Previously, where multiple blocks were executed in a single kernel run on the rollup side - the ticks of a block would be counted again in each subsequent block within the same run.

This resulted in a divergence of ticks between the rollup and sequencer.

How

We add an explicit 'ticks per block' into a block_in_progress, which will be used for gas price adjustment. The estimated_ticks_in_run are used (as previously) for reboot scheduling

Manually testing the MR

Try a rebase?

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