Library has odd behavior if a user defined version flag is specified #2755
Description
Was converting an old app that had a --version flag to System.CommandLine. It seems that there's also a --version flag integrated into System.CommandLine, which was taking precedence. System.CommandLine should error if one of the specified root options interferes with one of the built in options.