cnspec exits when too much args are specified

[czunker]

Describe the bug
When we call cnspec from inside a GitHub action, the action might add an empty arg to the command, e.g.:

/usr/bin/docker run ... mondoo/cnspec  "scan" "docker" "image" "mondoo-test:0.1.0" "--output" "compact" "--score-threshold" "0" "--log-level" "debug" ""

This results in an error:

...
Status: Downloaded newer image for mondoo/cnspec:latest
Error: accepts 1 arg(s), received 2
Usage:
...

This happens, because the action allows the user to specify additional args/parameters:
https://github.com/mondoohq/actions/pull/40/files#diff-d39e3d8374eded08ccdff5f7a8615006dd4d646d94f4eea996e30dca97790669R42

But, when nothing is specified it results in an empty arg "".

To Reproduce
Steps to reproduce the behavior:

1. Re-run the job linked below
2. Wait
3. See error

Expected behavior
cnspec should ignore the empty arg.

Additional context

Failed action job: https://github.com/mondoohq/actions/actions/runs/3419398794/jobs/5692869897

Looks similar to this one: actions/runner#924

[czunker]

The fix mondoohq/cnquery#453 would be needed for each action command.

The other option would be to remove the optional args from the GitHub action.

@scottford-io / @chris-rock Opinions?

[chris-rock]

That is a problem that needs to be fixed in the GitHub action. This would add a wrong behaviour to cnquery / cnspec