CLI: Unit test to ensure no argument name or alias collisions exist

[dkbennett]

Summary of the Pull Request

Simple test that walks the CLI command tree and ensures no commands have ambiguous names or aliases that map to different arguments.

Example of finding a collision (I intentionally gave session the same alias as help to force a collision)

Example of no collisions (the above alias removed)

PR Checklist

• Closes: Link to issue #xxx
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated if needed and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated if needed
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Walks the command tree from the Root and examines arguments of each command and ensures there are no duplicate names or aliases in any of them.

Validation Steps Performed

Test passes!

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a CLI unit test that walks the command tree from the root and asserts that argument names and aliases are unique per command, preventing ambiguous CLI argument parsing.

Changes:

• Added a breadth/depth traversal over the CLI command tree starting at RootCommand.
• Added per-command checks for duplicate argument long names and short aliases.

[AmelBawa-msft]

Approve with suggestions

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.