Implement Execution Tracing for Contract Call Operations

[danielbate]

In #3704 we showed how the script data from a contract call could be used to show the relevant call operations, however this was limited to the first function call. #3710 subsequently followed this to show how param1 and param2 from the call receipt could be used in conjunction with the script data to enable multi-call operations. However, this approach is dependent on a fixed max inputs value.

A more robust approach is to implement the execution tracing tool. This allows us to step through the transaction execution at each stage in the VM, allowing us to decode arguments and return data.

For this issue we need to understand:

• The full capabilities of the execution tracing tool
• How it would be integrated with the SDK
• How this tool would be used to build out multiple contract call operations

Important

We must be mindful of performance here, this may require an additional network call and therfore we may want to make the complete summary opt-in.

[danielbate]

We should enable a number of the tests from #3734 to prove this piece.