Note explorer action should now be used like this:

- type          : command@1
  name          :  Open in Windows File Explorer
  command       : explorer
  arguments     : '{{ repository.path }}'

I tried to run:

- type          : command@1
  name          : Open in Visual Studio Code
  command       : code
  arguments     : '"{{ repository.path }}"'
  active        : file.file_exists(exe_vs_code)

Because I have VSCode installed from the Windows Store, apparently it didn't get added to the PATH environment variable.
And Windows Terminal was configured to use an old inexistent font style for CMD.exe. (I almost never use CMD.exe so I didn't notice it when I imported the profile from my old system.)

There two ways RepoM tries to run a command:

1. First method uses the .NET native method, which is similar to using the Run:
   
   This method would've worked if code was in the PATH variable. Because in my case it wasn't, the method failed so it tried to use the second method.
2. Second method uses the shell. Basically it's the equivalent of typing the command in a cmd.exe window. This works and manages to start code , but because the cmd.exe profile in Windows Terminal is misconfigured, it shows a Windows Terminal error.

My fix adjust the second method by disabling the cmd.exe window. So if cmd.exe is misconfigured in Terminal, it doesn't matter because the cmd.exe window never tries to start, it just runs in the background.

The second fix that I introduced is checking the process object for NULL. This is a problem with the second method as sometimes it doesn't throw an error. For example, the following can fail to start with the first method, it tries the second method, and then fails with no error if the cmd.exe window is disabled:

- type: command@1
  name: Open in Windows File Explorer
  command: '"{{ repository.path }}"'

This is why we should always check for NULL.
Also, a fix to that is using:

- type          : command@1
  name          : Open in Windows File Explorer
  command       : explorer
  arguments     : '{{ repository.path }}'

This means the first method will always succeed and it won't have to try the second method, therefore also improving efficiency.

The rest of what I did is just improve logging. If both methods fail, then the errors from both attempts are logged as errors. If one succeeds, then they are logged as mere Information.