handle "run" command in the skip/only setting

[prog-supdex]

Closes #598

⚡ Summary

Added the ability to handle "run" commands in "skip" and "only" sections.

There are a few restrictions

1. We can only put one "run" command in skip/only sections because skip/only parses like a mapstructure. So we can't write
   skip
   - run: test "${NO_DAST}" -eq 1
   - run: npx is-ci
   - ref: dev/*
   `

2. In this PR, we can't put the command with pipelines (&&, &, || etc.), like this test "${NO_DAST}" -eq 1 && test ...., because this command is executed via exec.Command(cmdName, cmdArgs...), which accepts the first argument as the command and the rest of the argument as the command arguments.

3. Since only is the opposite of skip, if the run command returns true for the skip section, it will skip, but for the only section, it must return false.

☑️ Checklist

• Check locally
• Add tests
• Add documentation

[mrexox]

I like the results. It would be nice to have integrity tests (within testdata/ folder) but it looks great.

A few nitpicks related to naming and argument passing.

[mrexox]

I've tested the PR with the following config:

skip:
  skip:
    - run: test -z $VAR
  commands:
    echo:
      run: echo "should not be printed - $VAR"

VAR=1 lefthook run skip -v

But it always prints VAR whenever it is set or not.

I think the problem is that the arguments are passes as raw args to a cmd. Maybe it makes sense to wrap the commandLine with sh -c the way we do it in exec_unix.go.

The only concern I have regarding this is that on Windows the feature may not work. But anyway $VAR is sh syntax, not a system syntax, so it makes sense to me.

[prog-supdex]

@mrexox I added calling the command via sh -c but as you said, it may not work with Windows if it does not include WSL, Cygwin, and so on.

So I added checking the OS, but I couldn't check it because we don't have a running test-integrity for windows here

I think there was a reason why it was not added to ci-cd for windows :)
But what do you think about checking the windows and adding test integrity for Windows to ci-cd?

[mrexox]

Let's try it out!

[prog-supdex]

@mrexox, Unfortunately, the `[windows] skip' command was necessary to skip some of the Windows test integrations.

Also, I use PowerShell for Windows commands because it supports more complex commands (e.g. with if).

We can avoid skipping some test-integrities, but it requires adapting those tests, and it is difficult without a Windows machine.

The example of skipping test here

[prog-supdex]

but we checked the skip run for Windows, and it's working.
I added the separated file skip_run_windows for it

[mrexox]

Alright, I think this is acceptable for now. Thank you for digging into testscript, I appreciate it. I will try to figure out how to make it work for Windows when I have a chance to work on a Windows machine.