Add console.log option. Closes #981.

[jdforsythe]

Add option to console transport to use console.log/error instead
of writing to process.stdout/stderr.

Fixes issues like: microsoft/vscode#19750

[atif089]

@DrYSG last release has been like 7 months ago and not sure when the next release would be. If you already found another library to replace this I'd love to know.

[indexzero]

Thank you for your contribution!

Looks like the VSCode folks have fixed this upstream for all logging libraries, going to close this.

I agree with this sentiment on the issue.

[kletkeman]

The solution for the launch configuration:

"outputCapture": "std",

works perfectly! Thanks to anyone and everyone who made that happen ... I have been tortured by that for two days.

[baybal]

@indexzero well, I don't. The thing is even if VSCode itself does monkeypath around this for its own internal use, others don't.

Two solutions are on the table:

1. This one - let the user decide whether to use OS or V8 console
2. Separate the console and stdout transports as two fundamentally different things - one passes on inspection protocol data, other don't

[szolnokit]

Added a "forceConsole" option, to force use "console.log"

0757afe

[wbt]

The linked commit is in #2276 for better cross-referencing.