Do not use deprecated logger API

[isidorn]

@jrieken removed this morning the Logger API via 1c72ab2
This casued debugging to no longer work - just start debugging and you would get an exception (out of source).

The issue is that node-debug2 depends on the Logger which is proposed api. There are alternative solutions which we could use.
Also adding @weinand in case he is using the Logger in his extensions

Assigning to August since we should tackle this this week hopefully. If you do not have time let me know and I can look into it.
Once this is done, @jrieken can remove the Logger, for now we have reverted the change that removes the Logger

[weinand]

Both node debuggers use the proposed logger API.

@jrieken has already reverted the removal.

Since the plan is to move the logger API from the extensionContext to the output channel, we'll have to wait for this adoption until the API becomes available at the new location.

@roblourens are you taking care of moving your old Logger API to the output channel?

[jrieken]

we'll have to wait for this adoption until the API becomes available at the new location.

You can use appendLine already today

[roblourens]

Node2 doesn't use that logger API. We have our own logger that runs in the DA and writes to a file. We only use the logDirectory property which is becoming stabilized.

[roblourens]

node-debug does use the logger in a few places: https://github.com/Microsoft/vscode-node-debug/blob/master/src/node/extension/configurationProvider.ts#L88

[weinand]

@jrieken I've moved node-debug off the Logger API and node-debug no longer uses proposed API.