Display Emitted Events Along Execution Paths in TUI

Background:
Many Solidity developers, myself included, utilize emitted events as a method akin to printf debugging. This aids in quickly discerning execution paths, checking the state of variables without diving into storage, and providing a clear insight into contract behavior.

Feature Description:
Introduce a way to visualize emitted events along execution paths, similar to how we currently display constraints.
Allow developers to insert event emits and view these logs directly in the TUI.

The events are stored in the <log/> cell of the <substate/> cell. They are not logged in human-readable form, so to achieve readability we should look up the event digest and data types in the ABI so that we can display the event name used in Solidity, and ideally also the emitted data in a useful format (a libary like eth-abi might be useful here: https://eth-abi.readthedocs.io/en/latest/decoding.html ).

Benefit:
This enhancement would provide an immediate and certain way to answer questions like "how far did I get?" during contract execution. It would offer a more intuitive and certain alternative to the often ambiguous reasoning derived from analyzing nodes in the execution.

Start by tracing how the TUI displays constraints along execution paths, then inspect the substate log cell and the ABI data available for event decoding. Done means emitted events appear along the relevant paths in the TUI with Solidity event names and useful decoded data.