Add native call tracer

[natebeauregard]

Changes

Adds a native call tracer implementation to the nethermind client. The callTracer tracks all the call frames executed during a transaction, including depth 0. The result will be a nested list of call frames, resembling how EVM works. They form a tree with the top-level call at root and sub-calls as children of the higher levels.

Users can conditionally only select the main call or add emitted logs to the call stack as well depending on the tracerConfig that they pass in.

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Documentation

Requires explanation in Release Notes

• Yes
• No

The ReportOperationLog method and IsTracingOpLevelLogs flag was added to the ITxTracer interface to allow tracing logs emitted at the operation level.

[LukaszRozmej]

@benaadams we need your review on VirtualMachine stuff

[natebeauregard]

@LukaszRozmej I added a commit to update all of the list fields to use ArrayPoolList and then dispose of the array pools after the trace is serialized. Also, while conducting some final testing I noticed a bug where SELFDESTRUCT opcodes were being returned in a child call frame for the geth traces but not in nethermind so I added some additional logic to our call tracer to support that behavior.

Since some of these updates were non-trivial, especially in regards to the ArrayPoolList disposals, would you be able to look over the recent commits (Use ArrayPoolList for list objects, Fix selfdestruct bug) to see if you have any additional concerns prior to merging this?