[evm-tracing-0] add evm-tracing test suite to e2e ts tests

[dmitrylavrenov]

[dmitrylavrenov]

@MOZGIII

I would like to finalize the code we would like to have as a part of TDD for EVM tracing logic. At the current moment it's unclear to me what exactly should we have.

I started preparing a proper test to execute RPC request for debug_traceCall and discovered that current moonbeam implementation doesn't meet debug trace call specification. For example, tracerConfig doesn't contain enableReturnData at moonebeam version, but the spec tracerConfig does.

I was thinking in terms of TDD that we should take the specification and implement some simple tests at least that follow the spec. But it can be different from moonbeam implementation, like request call data type. So, I guess we should define request/response types and test data at least.

Currently I started with a374702.

[dmitrylavrenov]

@MOZGIII

I would like to finalize the code we would like to have as a part of TDD for EVM tracing logic. At the current moment it's unclear to me what exactly should we have.

I started preparing a proper test to execute RPC request for debug_traceCall and discovered that current moonbeam implementation doesn't meet debug trace call specification. For example, tracerConfig doesn't contain enableReturnData at moonebeam version, but the spec tracerConfig does.

I was thinking in terms of TDD that we should take the specification and implement some simple tests at least that follow the spec. But it can be different from moonbeam implementation, like request call data type. So, I guess we should define request/response types and test data at least.

Currently I started with a374702.

Separated the PR, moved the tests itself logic to #1575

[dmitrylavrenov]

Will rebase after #1580