CommandAlias conflicts with parent CommandAlias

[WeihanLi]

Got exception when the subcommand has same short command alias as parent command.

similar command structure

[CliCommand(Name = "bitbucket", Description = "Bitbucket related")]
public class BitbucketCommand
{
    [CliCommand(Name = "build", Description = "Trigger pipeline build for component")]
    public class BuildCommand
}    

error message

 System.Exception: CommandAlias "b" for "BuildCommand" conflicts with parent CommandAlias for "BitbucketCommand"

Since they're in different level, should be acceptable? If not, could we validate on build so that we could got error reported before publishing

[calacayir]

We do this check because System.CommandLine can crash if parent and child command has same name/short name (due to parsing from left to right I guess). I will check if we can add some improvements.

[calacayir]

Ok we solve this issue with v3.7.0:

Redesigned CliNamer class.

No short form alias will be added if a non-conflicting one can not be found, user can manually set a specific alias for these missing ones.

More robust handling of conflicts in CliNamer, i.e. checks all conflicts at once and then throws an exception which
lists all errors.