Remove pooled Stopwatch

Fix link in readme

Add 'using' misplacement fixer to code-cleanup

SharedStopwatch already offers a more efficient alternative.

- Microsoft.Net.Compilers.Toolset: 3.7.0-1.20254.1 -> 3.7.0-2.20259.1
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

Relates to #44102

When caching dependent-type-results, don't try to re-infer the originating project.

Code fix for CS0109 (The new keyword is not required)

Remove changes to XAML and F# IInlineRenameInfo interfaces

Skip executing analyzers by default on local builds for solutions in the repo

 Exclude csc.exe from optprof profiling 

Cache export provider factories

This reverts commit 71716fd5.

This change skips executing analyzers by default on explicit builds (both inside VS and on command line prompt). This should speed up the overall build time of Roslyn.sln when building locally.

The only time a developer would want analyzers to run locally outside the typing scenario is to compute the exact set of warnings for a specific project/solution before pushing your local changes to CI. They can now perform the following steps to achieve this:
1. On command line: Build with `/p:UseRoslynAnalyzers=true` or `/p:RunCodeAnalysis=true`
2. Inside VS:
   1. Start VS with `%RoslynEnforceCodeStyle% = true`, all builds in VS should execute analyzers
   2. Use `Run Code Analysis` command from `Analyze` menu on selected project/solution

Merge release/dev16.7-preview1 to master

Fix regression using alias qualified name in an is-type expression

Merge release/dev16.7-preview1 to master

Use a shared shadow copy assembly loader for all VisualStudioAnalyzer…

Fixes #44019

🧹 Remove duplicate calls to ThrowIfCancellationRequested