fix(vm): rollback builder state on failed Osaka blob tx (Fixes issue #4271)

[rame3519]

Summary:

Fixes a non-atomic failure path in BlockBuilder.addTransaction() where malformed Osaka blob transactions could partially mutate builder state before post-run validation failed.

Problem:

A Prague-created blob tx wrapped as an EIP-7594 network wrapper could:

• execute successfully via runTx()
• mutate VM state
• increment blobGasUsed
• later fail Osaka validation during createMinimal4844TxFromNetworkWrapper()

This left the builder in a poisoned state despite the transaction being rejected.

Fix:

• moved Osaka blob validation before runTx()
• added rollback protection for builder accounting/state
• restored transaction arrays and gas accounting on failure
• added regression coverage proving rollback correctness

Validation:

Added regression test:

ethjs-osaka-builder-state-poison.spec.ts

Before fix:

• invalid block stateRoot
• poisoned blobGasUsed
• replay failure

After fix:

• clean rollback
• blobGasUsed remains zero
• block replay succeeds

[holgerd77]

Hi there, thanks for the PR. What is your motivation to fix this?

[rame3519]

Hi there, thanks for the PR. What is your motivation to fix this?

Hello! Thanks for reaching out to me. This fix was for my Blockchains & Cryptocurrencies group project which required us to fix a related git project issue.