Prefer the expected path over any old git-bash on Windows

In some environments (e.g. if you're building Chromium from scratch) you
might have a totally unrelated git-bash command in your $PATH. That
breaks terminal interception: with this if git-bash is installed in the
normal way then it'll work regardless.

Author: pimterry

src/interceptors/terminal/fresh-terminal-interceptor.ts

@@ -39,10 +39,10 @@ const getTerminalCommand = _.memoize(async (): Promise<SpawnArgs | null> => {
 });
 
 const getWindowsTerminalCommand = async (): Promise<SpawnArgs | null> => {
-    if (await commandExists('git-bash')) {
-        return { command: 'git-bash' };
-    } else if (await canAccess(DEFAULT_GIT_BASH_PATH)) {
+    if (await canAccess(DEFAULT_GIT_BASH_PATH)) {
         return { command: DEFAULT_GIT_BASH_PATH };
+    } else if (await commandExists('git-bash')) {
+        return { command: 'git-bash' };
     }
 
     return { command: 'start', args: ['cmd'], options: { shell: true }, skipStartupScripts: true };