[system-command-line] instantiate logic

[vlada-shubina]

Problem

#3809

Outstanding (to be solved in different PR):

• ambiguous template group logic
• ambiguous template logic
• error handing for invalid parameters (it needs to take into account possible combinations from other template groups)
• tab completion
• error handling for alias assignment
• parsing hex params (low prio)
• invalid template logic (duplicate parameters etc)
• invalid parameters on exec time (low prio, unlikely to happen)
• show --allow-scripts only if the template has run-script post action

Outstanding (likely to be done in this PR)

• unit tests

Solution

basic solution for instantiate template (including basic help).

Checks:

• Added unit tests
• Added #nullable enable to all the modified files ?

[DavidKarlas]

What does "unlikely" means here? Never(should we throw exception)?

[vlada-shubina]

previously we did validation only for choice parameters on CLI level and didn't check if mandatory parameters are specified. So we end up in this code pretty often.

Now we do validation for all kinds of parameters on the parser level. So if we do job right, this should not happen. But in case logic of validation diverges in parser and core we might end up here.

Imo it's best to display Edge error here as we don't know the reason. Possible improvement is to separate invalid parameters and reason in Edge. Then we can do display reason, and convert canonical (name in json) parameter name to alias not to confuse user with canonical name. Edge doesn't know the alias name (this is CLI specific).

[DavidKarlas]

I think we dicussed this, if 2 groups have same ShortName, for both groups instead of shortname we display GroupdId.