Fixed issue with Parametric commands failing due to CommandArgs not being in namespace.

[me4502]

Currently, if you try to setup Parametric commands, it fails due to the DefaultModule expecting CommandArgs to be in the namespace when parser.parseArguments is called. This moves it to where it's defined, meaning it's available.

[literalplus]

I'm experiencing this issue too and looked into it before I found this.

Any reason we can't use the CommandArgs parameter passed to CommandArgsProvider directly? It seems to go through OptionType#transform(CommandArgs), but that shouldn't matter since declaring the CommandArgs parameter as @Switch or @Optional makes little to no sense, which means that the CommandArgs passed as parameter should generally be the same as these in the Namespace.