[ts-command-line] Prevent ambiguous abbreviations of parameters defined on parent tool or action

[D4N14L]

Summary

Consider parameters defined on the parent tool and (if applicable) parent action when preventing ambiguous parameter usage or ambiguous parameter abbreviations.

Details

Previously, it was possible to define a parameter on a parent tool or action, and not have an error thrown when the child action declares either an identical parameter or a parameter that has an ambiguous abbreviation when considering the parent parameters.

Ex. Given a tool heft with a defined parameter --debug and a defined action test with a defined parameter --debug:

• heft --debug test and heft test --debug are valid invocations of the heft tool, but the parameters would be handled differently
• Similarly, heft --debug test --debug would also be considered a valid command

This also applies to the automatic abbreviations that are supported by ts-command-line.

Ex. Given a tool heft with a defined parameter --debug and a defined action test with a defined parameter --debug-mode:

• heft --debug test and heft test --debug are valid invocations of the heft tool, but the parameters would be handled differently
• Similarly, heft --debug test --debug would also be considered a valid command

With this change, parent parameters are considered when looking for ambiguous parameter references.

Ex. Given a tool heft with a defined parameter --debug and a defined action test:

• Defining a parameter --debug on the test action will throw an error regarding duplicate parameters
• Defining a parameter --debug-mode on the test action is valid
  • heft --debug test is still valid
  • heft test --debug will throw an error regarding ambiguous parameter usage
  • heft test --debug- is valid, as it is an unambiguous abbreviation of the --debug-mode parameter
     

How it was tested

Added a bunch of unit tests.

Impacted documentation

May require updating website docs on ts-command-line