Add coverage detection on WindowsLocalCommandExecutor

[olperr1]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?

No

What kind of change does this PR introduce?

Quality (kind of)

What is the current behavior?

Existing unit tests on WindowsLocalCommandExecutor are run on Windows machine only.
Our workflow executes on Unix, Windows and MacOS, but the code coverage is only computed on Unix. Therefore WindowsLocalCommandExecutor appears as non-tested.

What is the new behavior (if this is a feature change)?
All the WindowsLocalCommandExecutor that don't finally execute a system command are run on every OS. As a consequence, they are taken into account for the code coverage.

Does this PR introduce a breaking change or deprecate an API?

• Yes
• No

If yes, please check if the following requirements are fulfilled

• The Breaking Change or Deprecated label has been added
• The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud