Implement Disassembly View and InstructionBreakpoints

[colin-grant-work]

What it does

Leaving this as a draft for now, as there are some details I need to check to make sure instruction breakpoints are working correctly.

Addresses parts of #8136 by implementing InstructionBreakpoints and a disassembly view to and the return of the disassemble request.

This PR copies and adapts VSCode's implementation of the Disassembly View for Theia.

How to test

0. In general: use any debugger that supports the disassemble request, and confirm that the behavior in Theia is consistent with the behavior in VSCode.
1. For example...
2. Install the CDT-GDB VSCode plugin
3. Open this example workspace and execute the build task.
4. Set a breakpoint in a.cpp and start debugging.
5. When you hit a breakpoint, you should be able to open the context menu in the stack view and find the 'Open Disassembly View' command - it should also be available in the command palette.
6. Disassembly should load.
7. Scrolling should load more lines.

CQ

• CQ Approved

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines

[msujew]

Looks mostly good. I noticed some unexpected behavior in regards to disassembly breakpoints:

As far as I can tell, debugging directly in the disassembly view is not supported, right (that's what the icon indicates)? Anyway, these breakpoints cannot be removed, and clicking on the breakpoint sidebar in the disassembly view only adds more breakpoints, instead of removing the existing ones.

[colin-grant-work]

@JonasHelming, would you be willing to push a bit to get the CQ through?

[vince-fugnitto]

The CQ has been approved, thank you @JonasHelming for helping it get across the line 👍

[colin-grant-work]

@msujew, I pushed a change (and meant to mention it - sorry) that addresses your comments. I have modified the enablement of the commands that manipulate all breakpoints to be available when only instruction breakpoints are present. I have also (and this makes it harder to test my last claim ;-)) added code that prevents the creation of instruction breakpoints for sessions that don't support them - an improvement, I believe, over VSCode's code.

[msujew]

Great, looks good to me!

• Hitting a breakpoint in the C code lets us open the disassembly view via a context menu / command.
• Scrolling up/down in the disassembly view loads more instructions and (relatively accurate) changes the position within the list view.
• Breakpoints within the disassembly view are disabled for cdt-gdb, definitely an improvements compared to vscode.

We can't really test the functionality of breakpoints within the disassembly view, but I'm fine with revisiting this if there are any problems with it and some extension has mature support for it.