lage should fail on invalid commands, args and arg values

We had a recent ADO Tools failure that was passing garbage args to lage like:

lage info build ut --since refs/remotes/origin/master##vso[task.debug]Exit code 0 received from tool '/bin/bash' --production --verbose --grouped

However, lage seems to be too lenient with garbage / invalid, resulting in "false positives":

info Lage task runner - let's make it
verb filterPackages changed: 
verb filterPackages running with dependents
info 🏗 Summary
info 
info Nothing has been run.
info ----------------------------------------------
info Took a total of 0.14s to complete
Done in 0.79s.

This allows PRs that didn't build or run tests to appear to be "passing" but then broke master after merge.

I think lage should fail harder on invalid commands and args to both prevent CI from generating "false positives" and also more clearly highlight issues with tools, like this ADO tool issue.

Start by reproducing the invalid lage info build ut --since ... command shown in the issue and trace its command-line argument handling. The change is done when invalid commands, arguments, and argument values cause a nonzero exit instead of reporting successful completion; no files or tests are named in the issue.