[trace-view] Added support for displaying disassembly view

[awelc]

Description

This PR adds support for viewing disassembly of Move source code when available. It does not use DAP's 'disassemblyRequest` feature as it does not seem mature enough to be used in our production setting. The particular problems discovered when trying to use it were:

• difficulty to properly refresh the disassembly view when moving between disassembly located in different files
• difficulty in controlling disassembly<->source transitions
• difficulty in controlling how disassembly input looks like (in particular if trying to add "invalid" instructions surrounding the disassembly to satisfy number of instructions to be returned as per VSCode-specified requirements passed in disassemblyRequest)

The gist of this solution is to maintain two views of the trace state, one reflecting "source" execution and one (optional), reflecting "bytecode" execution". The two main differences between these views are:

• local variable display: "source" view uses source-level variable names and hides "artificial" variables (generated by the compiler to support enums/macros), whereas "bytecode" displays all variables and uses their bytecode-level names
• a line of source/bytecode being executed at stop points

Breakpoints are also handles separately for different views (i.e., source/bytecode-level breakpoints only work in frames that show source/bytecode, respectively).

Test plan

A new test for disassembly-level stepping, breakpoints and variable display has been added. All remaining tests must pass

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sui-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 23, 2025 1:43am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
multisig-toolkit	⬜️ Ignored (Inspect)	Visit Preview		Jan 23, 2025 1:43am
sui-kiosk	⬜️ Ignored (Inspect)	Visit Preview		Jan 23, 2025 1:43am