feat(jsonrpc/trace): add createType for parity traces

[jsvisa]

similiar to ethereum/go-ethereum#30539 add createType for the create traces.

[mriccobene]

Please, to fix RPC Integration tests on this PR try changing the workflow at this line using --branch feature/add_createtype_for_parity_traces

[jsvisa]

@mriccobene sorry for the inconvenience, for the compatibly reason, we may name it from createType to creationMethod, so I'll change erigon's code after geth's got merged(ref ethereum/go-ethereum#30539 (comment)).

[mriccobene]

@jsvisa can you contribute to my branch by changing the method name accordingly, from createType to creationMethod or as you decided, in the failing tests? you can look at my commit and do the same.

[jsvisa]

@jsvisa can you contribute to my branch by changing the method name accordingly, from createType to creationMethod or as you decided, in the failing tests? you can look at my commit and do the same.

yeah, sounds good to me. May I ask, if this means I can file a PR and set the destination branch as https://github.com/erigontech/rpc-tests/tree/feature/add_createtype_for_parity_traces, or based on the add_createtype_for_parity_traces branch, and send another PR to in https://github.com/erigontech/rpc-tests

[mriccobene]

May I ask, if this means I can file a PR and set the destination branch as [...], or based on the add_createtype_for_parity_traces branch, and send another PR to in https://github.com/erigontech/rpc-tests

I think it's easier to create a new PR on a fresh branch; my branch can only help you as a guide. Note that in the test run log you can see the failed tests and in the test run artifacts there are the files with the expected and actual values ​​- these files can serve you instead of my branch to fix the failing tests