Create visual rendering of diagnostic events

[janewang]

Create section based on diagnostic events.

The Vision
The eventual goal of this section is to show the execution trace by stepping through the WASM. There is a possibility to convert WASM into WASM Text (WAT), and be able to show on how the code execution path. Eventually with a sourcemap, we can connect the WAT to the actual Rust source code. However, this is currently missing and we do not have sourcemap of Rust to WASM.

What is possible Today
What is possible today is to reconstruct the functional calls and events into an execution tree. Likely we are not able to show internal contract calls, but it is possible to show external contract calls, and associated events. In some ways, Stellar Expert seeks to do this: example. But it appears that the contract invocation and related events that are raised are out of order.

[leighmcculloch]

Some feedback on the design screenshot:

• The return value should be visible for each function call.
• Each fn call line can we remove the 'params' word and the _address, so that it is transfer(from: ...) that will look more like natural function calls.
• I'm also wondering if we can put the contract and fn call on one line, so there's one line per call so it would be more like call: CABC.transfer(from: ...)
• Love that events are included.

[janewang]

An example of trace: https://gist.github.com/janewang/b3e6c2edac0ed8676c06e038df636507

[janewang]

@quietbits let's have a chat when you are ready to pick up on this