Fix #145: cli parsing - handle correctly false value for validator

[yoavain]

Description

When adding a validator boolean flag to command line, the value was ignored, and the validator was activated even if its value was "false".

Types of changes

• Fixed some CLI tests failing on Windows with "Error: spawn UNKNOWN" due to running with childProcess.spawn(cliExecPath, [...]). Changed to childProcess.spawn('node', [cliExecPath, ...])
• Added validator only if commandValue is not falsy
• Added tests to make sure validator does not run when flag is missing, or flag is set to "false"
• Added another cli test for the integrity validator

Note: This does not resolve command-line with typos.

• [X] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [X] Breaking change (fix or feature that would cause existing functionality to change)

Related Issue

https://github.com/lirantal/lockfile-lint/issues/145

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Checklist:

• [ ] I have updated the documentation (if required).
• [X] I have read the CONTRIBUTING document.
• [X] I have added tests to cover my changes.
• [X] All new and existing tests passed.
• [ ] I added a picture of a cute animal cause it's fun

[codecov-commenter]

Codecov Report

Base: 97.95% // Head: 97.95% // No change to project coverage :thumbsup:

Coverage data is based on head (fcba2a9) compared to base (a29d18b). Patch has no changes to coverable lines.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #146 +/- ## ======================================= Coverage 97.95% 97.95% ======================================= Files 13 13 Lines 342 342 Branches 73 73 ======================================= Hits 335 335 Misses 7 7 ``` Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Liran+Tal). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Liran+Tal)

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

[lirantal]

Thanks @yoavain 👏

Overall looks ok, but I was wondering if this won't cause an issue with the --empty-hostname validator which on falsy value actually enables a stricter check? I'll check the code really quickly myself too but wanted to float that before merging.

So basically referring to this:

        if (!isPassing) {
          if (!packageResolvedURL.host && options && options.emptyHostname) {
            this.debug(`detected empty hostname but allowing because emptyHostname is not false`)

[lirantal]

Anyway, looks ok to me to merge but let me know if you think otherwise.

[yoavain]

@lirantal I think the change only affects the flags in supportedValidators. empty-hostname is not in that map

[lirantal]

You're right, I see it passed in later as the option to the validators. Let's land it then.