PowerShell session commands should activate extension

This change fixes #1020 which states that PowerShell session commands
should activate the extension if it isn't already started.  These
commands are useful for activating a PowerShell session if the user
doesn't currently have a PowerShell file open.

Author: daviwil

package.json

@@ -32,7 +32,9 @@
     "onCommand:PowerShell.StartDebugSession",
     "onCommand:PowerShell.PickPSHostProcess",
     "onCommand:PowerShell.SpecifyScriptArgs",
-    "onCommand:PowerShell.ShowSessionConsole"
+    "onCommand:PowerShell.ShowSessionConsole",
+    "onCommand:PowerShell.ShowSessionMenu",
+    "onCommand:PowerShell.RestartSession"
   ],
   "dependencies": {
     "vscode-languageclient": "3.3.0-alpha.6"

src/session.ts

@@ -628,14 +628,6 @@ export class SessionManager implements Middleware {
     private showSessionMenu() {
         var menuItems: SessionMenuItem[] = [];
 
-        if (this.sessionStatus === SessionStatus.Initializing ||
-            this.sessionStatus === SessionStatus.NotStarted ||
-            this.sessionStatus === SessionStatus.Stopping) {
-
-            // Don't show a menu for these states
-            return;
-        }
-
         if (this.sessionStatus === SessionStatus.Running) {
             menuItems = [
                 new SessionMenuItem(
@@ -655,7 +647,7 @@ export class SessionManager implements Middleware {
             ];
         }
 
-        var currentExePath = this.powerShellExePath.toLowerCase();
+        var currentExePath = (this.powerShellExePath || "").toLowerCase();
         var powerShellItems =
             getAvailablePowerShellExes(this.platformDetails)
                 .filter(item => item.exePath.toLowerCase() !== currentExePath)