Test: Show breakpoint diagnostic info in debugger UI

[roblourens]

Refs: #142870

• macOS @deepak1556
• linux @gregvanl
• windows @DonJayamanne

Complexity: 2

Create Issue

---

• Start debugging a js/ts program
• Set a breakpoint in a .ts or .js file that is not loaded by the debuggee. Or, purposely break your sourcemap config so that .ts sourcemapped files can not be mapped by vscode.
• After several seconds, a warning indicator should appear in the breakpoints view header
  
• Hovering it shows a message from js-debug with a command link to launch the debug diagnostic editor.
• Hovering the gray circle breakpoint in the editor shows the same message

---

• Try the same scenario, but with setting a breakpoint in a file of a language which is not handled by js-debug, such as a .py file
• The breakpoint will turn gray but you should not see the warning indicator about unbound breakpoints

[roblourens]

The js-debug PR will land in June, and since this doesn't actually appear in vscode yet, we can just test this in June

[roblourens]

This got assigned anyway even though it wasn't on the milestone