Make the Verbosity enum normal

[baronfel]

No description provided.

[KalleOlaviNiemitalo]

Does this fix the following error with 10.0.100-rc.1.25451.107:

C:\>dotnet package search --verbosity=normal ValueTuple
System.InvalidCastException: Specified cast is not valid.
   at System.CommandLine.Binding.ArgumentConverter.ConvertObject(ArgumentResult argumentResult, Type type, Object value)
   at System.CommandLine.Binding.ArgumentConverter.ConvertIfNeeded(ArgumentConversionResult conversionResult, Type toType)
   at System.CommandLine.Parsing.OptionResult.GetValueOrDefault[T]()
   at System.CommandLine.Parsing.SymbolResult.GetValue[T](String name)
   at Microsoft.DotNet.Cli.Extensions.ParseResultExtensions.SafelyGetValueForOption[T](ParseResult parseResult, String name)
   at Microsoft.DotNet.Cli.Telemetry.TelemetryFilter.LogVerbosityForAllTopLevelCommand(ICollection`1 result, ParseResult parseResult, String topLevelCommandName, Dictionary`2 measurements)
   at Microsoft.DotNet.Cli.Telemetry.TelemetryFilter.Filter(Object objectToFilter)
   at Microsoft.DotNet.Cli.Utils.TelemetryEventEntry.SendFiltered(Object o)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, TimeSpan startupTime)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)

[baronfel]

Does this fix the following error with 10.0.100-rc.1.25451.107:

C:\>dotnet package search --verbosity=normal ValueTuple
System.InvalidCastException: Specified cast is not valid.
   at System.CommandLine.Binding.ArgumentConverter.ConvertObject(ArgumentResult argumentResult, Type type, Object value)
   at System.CommandLine.Binding.ArgumentConverter.ConvertIfNeeded(ArgumentConversionResult conversionResult, Type toType)
   at System.CommandLine.Parsing.OptionResult.GetValueOrDefault[T]()
   at System.CommandLine.Parsing.SymbolResult.GetValue[T](String name)
   at Microsoft.DotNet.Cli.Extensions.ParseResultExtensions.SafelyGetValueForOption[T](ParseResult parseResult, String name)
   at Microsoft.DotNet.Cli.Telemetry.TelemetryFilter.LogVerbosityForAllTopLevelCommand(ICollection`1 result, ParseResult parseResult, String topLevelCommandName, Dictionary`2 measurements)
   at Microsoft.DotNet.Cli.Telemetry.TelemetryFilter.Filter(Object objectToFilter)
   at Microsoft.DotNet.Cli.Utils.TelemetryEventEntry.SendFiltered(Object o)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, TimeSpan startupTime)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)

We fixed this separately by making that component more tolerant, but yes this does unify the representation of verbosity across the entire codebase.

[Copilot]

Pull Request Overview

This PR refactors the verbosity option handling in the .NET CLI by replacing the VerbosityOptions enum with a new Verbosity enum and implementing custom parsing logic. The main changes include:

• Replacing VerbosityOptions enum (with aliases like q, m, n, d, diag) with a cleaner Verbosity enum containing only the full names
• Adding custom parsing logic to support shorthand values like "q", "m", "n", "d", "diag"
• Improving error messages to be more descriptive
• Updating all completion scripts and localization files

Reviewed Changes

Copilot reviewed 93 out of 93 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/Cli/Microsoft.DotNet.Cli.Utils/Verbosity.cs	New enum and data class replacing VerbosityOptions
src/Cli/Microsoft.DotNet.Cli.Utils/VerbosityOptions.cs	Deleted old enum
src/Cli/dotnet/CommonOptions.cs	Added custom parser for verbosity with better error handling
src/Cli/dotnet/Extensions/CommonOptionsExtensions.cs	Simplified extension methods using new enum
src/Cli/dotnet/NugetPackageDownloader/NuGetPackageDownloader.cs	Refactored verbosity comparison logic
test/dotnet.Tests/CliSchemaTests.cs	Updated test snapshots for schema changes
test/dotnet.Tests/CompletionTests/snapshots/*	Updated completion script snapshots
src/Cli/dotnet/xlf/*.xlf	Updated localization files with new error messages

[Copilot]

[nitpick] The final line of the bash completion script has an unnecessary change from having a preceding blank line marker to not having one. This appears to be a formatting inconsistency that doesn't affect functionality but creates noise in the diff.

[baronfel]

Re-targeted this to release/10.0.2xx to get the unification benefits sooner and reduce churn between main and the 10.x series in the future.

[MiYanni]

I know I asked this in the past, but I forgot the answer. Is it necessary for these to be lowercase? It is just anti-C# style to have public things be entirely lowercase.

[MiYanni]

There was probably a name-clash reason that it was prefixed with Utils.. Does that clash still exist with Verbosity?