EVM/Node: generalise the simulation input type
What
Introduces a "versioned" type for simulation input
Why
It's cleaner and does the same thing. I wanna add a third version and it would be a nightmare without this type.
How
A goold old variant, we choose between V0 or V1 based on enabled_with_da_fees.
Manually testing the MR
CI should be enough
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.rstfor the protocol and the environment,CHANGES.rstat the root of the repository for everything else). -
Select suitable reviewers using the Reviewersfield below. -
Select as Assigneethe next person who should take action on that MR