consensus/parlia: set nonce before evm run

[buddh0]

Description

consensus/parlia: set nonce before evm run

Rationale

It's strange to set nonce after execute tx, so align with it in TransitionDb
no need to use hardfork to control, there are 3 reasons:

1. The GetNonce function will not be invoked during the execution process of the virtual machine, so placing it before or after the call execution has no impact.

2. Modifications to the state occur on a per-block basis, so placing them after Finalise also does not affect the overall result of block execution.

3. The journal is used for rollback purposes; transactions in Parlia will not revert, so the impact can be ignored.

Example

add an example CLI or API response...

Changes

Notable changes:

• add each change in a bullet point here
• ...

[maoueh]

I would like to raise the fact that while indeed that consensus will not break because of such change, it do breaks the determinism of our Firehose tracing system as it expects that the execution happens in the same order whatever version of the node you use.

Now if I reprocess with v1.3.8 to trace the full chain and again with v1.3.9 I will get different results because the SetNonce is not done at the exact same place.

I would like see if the BNB team would be open to revert the change. Seems that the only reason was to better align with Geth ways of doing things, so doesn't feel like it's a strict requirement for a bug fix of some upcoming feature.