feat(cheatcodes): improve `getStateDiff` output and add `getStateDiffStruct`

[grandizzy]

Component

Forge

Describe the feature you would like

follow up of #9435 / #2846
see #9435 (comment)

Tenderly sample
https://api.tenderly.co/api/v1/public-contract/1/trace/0x7abecacd8b1a54db8f0835a5c82edfab96ff922a41d2faa914c339e3e9319b43

• add Foundry contract name / artifact (along current label)
• add nonce diffs
• add sol type / storage labels and decode state diff (by using storage layout)
• add vm.getStateDiffStruct cheatcode that returns an array of structs to facilitate introspection directly in solidity

Additional context

No response

[sakulstra]

Hey, we just started using this feature and one thing i noticed is that on the returned json there are lots of "empty artifacts".

Not sure if that is by intention or not, but i assume no?

"0x5300a1a15135ea4dc7ad5a167152c01efc9b192a": {
      "label": null,
      "balanceDiff": null,
      "stateDiff": {}
    },

[sakulstra]

Another more severe issue seems to be "wrongly reported storage changes".
When using delegate call (e.g. via an oz proxy), the storage changes will be reported on the address of the implementation although they should be on the proxy calling the implementation.

[sakulstra]

add sol type / storage labels and decode state diff (by using storage layout)

@grandizzy is this sth on the short-mid term roadmap?
Working on some aave related tooling and am wondering if it makes sense to build on top of getStateDiff, or if it would be more rational to rely on tenderly/sim.io.

[grandizzy]

hey @sakulstra going to schedule it for next v1.4.0 version but cannot give you an exact timeline (we're wrapping up v1.3.0 this week and move forward)