Integrated Console doesn't start when missing powerShellExePath setting

[daviwil]

The latest VS Code Insiders builds have caused a change in behavior which causes the PS Integrated Console to not launch when the "powershell.powerShellExePath setting isn't specified. There must have been an API change related to default setting values.

[daviwil]

Wasn't actually able to reproduce this issue when I tried it, but I made sure that the correct default value will get sent through no matter what.