Test: debugger readMemory and writeMemory

[connor4312]

Refs: #126268

• anyOS @weinand
• anyOS @sbatten

Complexity: 4

Create Issue

---

This iteration, we (at long last!) added support for reading and writing binary data into VS Code and the Javascript Debugger (microsoft/vscode-js-debug#1167). To test:

1. Start without the hex editor installed in VS Code

2. Have a Node.js program that has binary data, for example:

   const crypto = require('crypto');
   const bytes = crypto.randomBytes(1024);
   debugger;
   console.log(bytes);

3. Run the program. In the Variables view, types that support binary data should have an inline binary icon on hover.

4. Click on the icon. You should be prompted to install the hex editor. Do so, and after you do a view showing the binary data should be automatically opened to the side.

5. Editing should work and be reflected in the program (e.g. in the REPL)

6. The hex editor should automatically close when the debug session ends.

Known issues:

• Editing a binary type in the hex editor won't automatically refresh the variables view. There's some debt to clear before this can be easily fixed -- next iteration.
• Hex editors are visible after unpausing the debugger, but (in js debug) causing them to reload will thereafter result in a blank editor. Should memoryReference reuse be explicitly suggested? debug-adapter-protocol#238