Test: link origin of messages in debug console

[isidorn]

Refs: #24490

• Windows - @dbaeumer
• OS X - @octref
• Linux - @chrmarti

Complexity: 3

We now support showing the origin of messages in debug console. Note that this is currently only supported by the node2 debug adapter. Have some nedo repository, for example our smoketest and if you have node below version 8 add "inspector": "protocol" to the launch configuration.

Verify:

• all output logged should appear in the debug console with a proper origin.
• clicking on the origin takes you to the appropriate file / line number / column

When using console.log, console.warn or console.error from an extension, the log information is serialised from the extension host to the renderer and then played back in the renderers DevTools console as well as debug console. This means that the origin of the console use from the extension is lost. We now preserve the origin and allow access to it.

Use console.log, console.warn or console.error from your extension with strings, objects, primitives etc. Have some extension repository and verify:

• you can expand the message in the extension host dev tools to see the full stack of where the message was sent
• you see the location of the message in the right hand side of the debug console and can click on it
• the data that you log is not shown up in a bad way or is lost