feat(`tracing`): decode constructor args when contracts are deployed in traces

[0xdapper]

Component

Forge

Describe the feature you would like

Currently, the forge traces do not decode the constructor args for contract creation. It'd be helpful for debugging if it showed decoded constructor args too.

Additional context

    │   │   │   │   ├─ [230190] → new UpgradeableBeacon@0xDD01220743f18cb611353924ff65af15B46979da

[zerosnacks]

Able to reproduce, makes sense to add it

Traces:
  [157871] CounterTest::setUp()
    ├─ [118761] → new Counter@0x5615dEB798BB3E4dFa0139dFa1b3D433Cc23b72f
    │   └─ ← [Return] 481 bytes of code
    ├─ [492] Counter::setNumber(0)
    │   └─ ← [Stop] 
    └─ ← [Stop] 

where

contract CounterTest is Test {
    Counter public counter;

    function setUp() public {
        counter = new Counter(42);
        counter.setNumber(0);
    }

    ...
}

contract Counter {
    uint256 public number;

    constructor(uint256 newNumber) {
        number = newNumber;
    }

    ...
}

[0xdapper]

Looked into this a bit while trying to implement. Didn't complete it, but I think it might not be as trivial, need some public api changes on crates that are not foundry. Changes I think are needed:

1. TraceWriterwhich is not part of this repo, but revm-inspectors
2. Store contract constructor abi params in CallTraceDecoder, probably in CallTraceDecoder::collect_identities.
3. But to decode the params, we also need to know how much of the initcode is the creation code and how much of it is the appended encoded params. So, we need to probably add a function somewhere(maybe in TraceIdentifier but doesn't go well with the name) that can return the init code or init code length taking the artifact_id.
4. After we have the constructor params abi, and the initcode length, we can take the compute the slice of initcode that is encoded params and decode it.
5. Should also decide how we want to print it? new Contract(arg1, arg2, ...)@0xadd4e55 or new Contract@0xadd4e55(arg1, arg2, ...) or some other format?