"Run tests" CodeLens invocation fails with "Error: command 'vscode.startDebug' not found"

[sebcanonica]

System Details

• Operating system name and version: Windows 8.1 Pro 6.3.9600
• VS Code version: 1.18.0
• PowerShell extension version: 1.5.0
• Output from $PSVersionTable:

> code -v
1.18.0
dcee2202709a4f223185514b9275aa4229841aa7

> $pseditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
1      5      0      0

> code --list-extensions --show-versions
dbaeumer.vscode-eslint@1.4.3
donjayamanne.javadebugger@0.1.5
ms-vscode.PowerShell@1.5.0
ms-vsts.team@1.122.0
redhat.java@0.14.0
shd101wyy.markdown-preview-enhanced@0.3.0
vscjava.vscode-java-debug@0.3.0
vscjava.vscode-java-pack@0.2.0

> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.14409.1012
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1012
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

When editing a Pester test file, clicking on the "Run tests" CodeLens brings back the Integrated Console to the foreground, but do not launch anything.

In the Electron "Developper Tools", the follwing error is written to the console:

/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10 command 'vscode.startDebug' not found: Error: command 'vscode.startDebug' not found
    at t._tryExecuteCommand (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1117177)
    at file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1117016
    at n.Class.define.cancel.then (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:69294)
    at t.executeCommand (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1116990)
    at e.$executeCommand (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:2822547)
    at t.e.invoke (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:2876274)
    at e._invokeHandler (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:2440074)
    at e._receiveOneMessage (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:2439764)
    at file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:2438791
    at file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:2440710

The startDebug command was removed by the VSCode project.
Related Issue: microsoft/vscode#33795