chore(Windows): add -TestsDebug parameter to build.ps1

[lemeurherve]

This PR introduces -TestsDebug parameter to build.ps1.

With it we can use -TestsDebug parameter or $env:TESTS_DEBUG to improve Windows tests debugging:

• As it can be passed in the Jenkinsfile, it's easy now to activate it on a build replay instead of having to add a commit to switch debug on or off.
• This parameter can take the following values:
  • empty/undefined: no additional debug (default value).
  • debug: output every test command and stderr on top of every test. (Equivalent of setting $quiet=$true in the test_helpers "Run-Program" function currently)
  • verbose: same as debug + output of stdout.

Output (from docker-ssh-agent pull request):

With .\build.ps1 test -TestsDebug 'debug':

With .\build.ps1 test -TestsDebug 'verbose':

Similar to:

• chore: improve Windows tests debug and small code cleanup docker-ssh-agent#396

Testing done

Local tests + CI

Replay with -TestsDebug set to "verbose" and only one Windows image type to validate the functionality:

• diff

  --- old/Jenkinsfile
  +++ new/Jenkinsfile
  @@ -24,7 +24,7 @@
                   axes {
                       axis {
                           name 'IMAGE_TYPE'
  -                        values 'linux', 'nanoserver-1809', 'nanoserver-ltsc2019', 'nanoserver-ltsc2022', 'windowsservercore-1809', 'windowsservercore-ltsc2019', 'windowsservercore-ltsc2022'
  +                        values 'nanoserver-1809'
                       }
                   }
                   stages {
  @@ -63,7 +63,7 @@
                                               // If the tests are passing for Linux AMD64, then we can build all the CPU architectures
                                               sh 'docker buildx bake --file docker-bake.hcl linux'
                                           } else {
  -                                            powershell '& ./build.ps1 test'
  +                                            powershell '& ./build.ps1 test -TestsDebug verbose'
                                           }
                                       }
                                   }

• https://ci.jenkins.io/job/Packaging/job/docker-agent/job/PR-828/2/

Submitter checklist

Beta Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

[lemeurherve]

Note: this change is also included in #827, I created this distinct pull request to check outputs while working on it.

Prefer reviewing #827 instead of this one.

[lemeurherve]

Closing in favor of #827