The docs say, in 1.19, VSCode made more fine-grained debugger activation events.

Read the link for the full details but the rule of thumb goes as followed:

Rule of thumb: If activation of a debug extensions is lightweight, use onDebug. If it is heavyweight, use onDebugInitialConfigurations and/or onDebugResolve depending on whether the DebugConfigurationProvider implements the corresponding methods provideDebugConfigurations and/or resolveDebugConfiguration.

The vscode-powershell extension implements just resolveDebugConfiguration here so we just need to replace onDebug with onDebugResolve:type

Resolves #1179