Added warning in case of invalid combination of command and flags and/or arguments

[ruvceskistefan]

Closes #1731

[thboop]

Love the tests!

[TingluoHuang]

do we need to add PAT to the Remove list?

[thboop]

we should!

[thboop]

Could we update the error message to provide more context.

1. If we can easily get the name of the command being run (or at least the first command if there are multiple we could do

terminal.WriteError($"Unrecognized command-line input arguments for command ${command}: '{string.Join(", ", unknownCommandlines)}'. For usage refer to: .\\config.cmd --help or ./config.sh --help");

2. I don't see an easy way to get the the command name in program.cs , so we could also:

terminal.WriteError($"This command does not recognize the command-line input arguments: '{string.Join(", ", unknownCommandlines)}'. For usage refer to: .\\config.cmd --help or ./config.sh --help");

[ruvceskistefan]

Could we update the error message to provide more context.

1. If we can easily get the name of the command being run (or at least the first command if there are multiple we could do

terminal.WriteError($"Unrecognized command-line input arguments for command ${command}: '{string.Join(", ", unknownCommandlines)}'. For usage refer to: .\\config.cmd --help or ./config.sh --help");

2. I don't see an easy way to get the the command name in program.cs , so we could also:

terminal.WriteError($"This command does not recognize the command-line input arguments: '{string.Join(", ", unknownCommandlines)}'. For usage refer to: .\\config.cmd --help or ./config.sh --help");

I can implement a method in the CommandSettings class that will return the command's name based on the flags Configure, Remove, Run, and Warmup, and then use that method in Program.cs.

[thboop]

lgtm