fix: patch create traces to work with foundry

[nbaztec]

Motivation

Unlike EVM, CREATE call traces obtained from zkEVM do not contain the bytecode in the output section but a 0-padded address instead. This causes the traces to not be decoded properly in foundry causing issues in gas reporting and invariant tests.

Solution

Patch zkEVM CREATE call trace to populate it with the bytecode, for better interoperability with foundry.

Now:

Traces:
  [32676] ZkTraceTest::testZkTraceOutputDuringCreate()
    ├─ [0] → new ConstructorAdder@0xF9E9ba9Ed9B96AB918c74B21dD0f1D5f2ac38a30
    │   ├─ [127] → new Number@0xf232f12E115391c535FD519B00efADf042fc8Be5
    │   │   └─ ← [Return] 2272 bytes of code
    │   ├─ [85280] Number::five()
    │   │   ├─ [91] → new InnerNumber@0xEd570f3F91621894E001DF0fB70BfbD123D3c8AD
    │   │   │   └─ ← [Return] 736 bytes of code
    │   │   ├─ [889] InnerNumber::innerFive()
    │   │   │   └─ ← [Return] 5
    │   │   └─ ← [Return] 5
    │   ├─ [74776] Number::five()
    │   │   ├─ [91] → new InnerNumber@0xAbceAEaC3d3a2ac3Dcffd7A60Ca00A3fAC9490cA
    │   │   │   └─ ← [Return] 736 bytes of code
    │   │   ├─ [889] InnerNumber::innerFive()
    │   │   │   └─ ← [Return] 5
    │   │   └─ ← [Return] 5
    │   ├─ [276] console::log(10)
    │   │   └─ ← [Return] 
    │   └─ ← [Return] 3168 bytes of code
    └─ ← [Stop] 

[Karrq]

Great work