Add verbosity option to run command.

This commit adds the verbosity option to the run command.

This will be used in tests for visibility into what the run command is
doing.

The default verbosity is unaffected.

Fixes issue #7932.

Author: Peter Huene

src/dotnet/commands/dotnet-run/RunCommandParser.cs

@@ -51,7 +51,8 @@ public static Command Run() =>
                         "--no-build",
                         LocalizableStrings.CommandOptionNoBuildDescription,
                         Accept.NoArguments()),
-                    CommonOptions.NoRestoreOption()
+                    CommonOptions.NoRestoreOption(),
+                    CommonOptions.VerbosityOption()
                 });
     }
 }

test/dotnet-run.Tests/GivenDotnetRunRunsCsProj.cs

@@ -518,5 +518,27 @@ public void ItPrintsAnErrorWhenLaunchSettingsAreCorrupted()
                 .And.HaveStdOutContaining("(NO MESSAGE)")
                 .And.HaveStdErrContaining(string.Format(LocalizableStrings.RunCommandExceptionCouldNotApplyLaunchSettings, LocalizableStrings.DefaultLaunchProfileDisplayName, "").Trim());
         }
+
+        [Fact]
+        public void ItRunsWithTheSpecifiedVerbosity()
+        {
+            var testAppName = "MSBuildTestApp";
+            var testInstance = TestAssets.Get(testAppName)
+                            .CreateInstance()
+                            .WithSourceFiles();
+
+            var result = new RunCommand()
+                .WithWorkingDirectory( testInstance.Root.FullName)
+                .ExecuteWithCapturedOutput("-v:n");
+
+            result.Should().Pass()
+                .And.HaveStdOutContaining("Hello World!");
+
+            if (!DotnetUnderTest.IsLocalized())
+            {
+                result.Should().HaveStdOutContaining("Restore")
+                    .And.HaveStdOutContaining("CoreCompile");
+            }
+        }
     }
 }