Add Find References unit tests for ContainingTypeInfo and ContainingM…

Ensure PackageInstallerService does not require the UI thread during GetSuggestedActions

Remove unnecessary DoEvents call

Simplify and make our code for resolving body-level symbols more resilient

Replace Generic Parameters with used Type Arguments in descriptions impl.

Only acquire IEditorOptionsFactoryService once for a contained document

Update roslyn-analyzers to enable non-copyable analyzer

* Add option page registration attributes back

* DiagnosticWindowPackage

Closes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1124280

Builds on #44240 to add FAR tests for more custom columns

[Dogfooding] Enforce IDE0060 (Remove unused parameter) as build warni…

Add FindReferences tests for Kind column/SymbolUsageInfo for references

Remove unused parameter

Refactoring "Move tool tip assertions to shared ToolTipAssert class" (commit 04968d4b) had to be applied to the new methods

* upstream/master: (1865 commits)
  Fix serialization/deserialization of SymbolUsageInfo in SerializableSourceReferenceItem
  [Dogfooding[ Enforce IDE0011 (Add braces) as a build warning for some IDE projects
  No longer add dumps by default (#44094)
  Fix crash in ref-returning property (#44186)
  Removing the workaround for https://github.com/dotnet/roslyn/issues/42166 identified that IDE0051/IDE0052 were not getting enforced on the build. I will file a follow-up issue to investigate it, but this commit fixes the existing IDE0051/IDE0052 violations in IDE projects where they are set to warning.
  Remove workaround added for https://github.com/dotnet/roslyn/issues/42166
  Fix example (#43910)
  Use stronger types in the formatter
  Use named tuple elements
  Convert a couple of PROTOTYPE comments that crept in via source generators (#44165)
  Fix stopwatch usage
  Remove unnecessary coupling
  Remove unnecessary value assignment
  Enforce parent type (as it was initially)
  Revert unused OptionsCollection in a test - this test does not use this options collection in master branch, but my prior commit in this PR attempted to use it in the test. This leads the test to fail, so I have restored the original semantics of the test and removed an unused local.
  Fixes PathMap parsing to support all paths (#43706)
  Revert temporary workaround for IDE0059 FixAll operation
  Manual fixes for IDE0059 violations for assignments of a non-constant value (we do not offer code fixes to remove such assignments which could have side effects)
  Apply FixAll in solution for IDE0059 (C# projects)
  Enable few more code style rules in IDE projects:
  ...

Use project.Name as the display name for Class View

Use named tuple elements

Remove workaround in build scripts for #42166

Use stronger types in the formatter

Fix serialization/deserialization of SymbolUsageInfo in SerializableS…

[Dogfooding] Enforce IDE0011 (Add braces) as a build warning for some…

Show progress bar for "Running code analysis on <Project/Solution>" execution

Fixes #44184
Find References "Kind" column uses `SymbolUsageInfo` for its data. `SymbolUsageInfo` is correctly serialized/deserialized when Find References is invoked via [SymbolFinder.FindReferencesServerCallback](https://github.com/dotnet/roslyn/blob/b8585be8e9ff9e30dbe64980e2c9156ae8b6c2bf/src/Workspaces/Core/Portable/FindSymbols/SymbolFinder.FindReferencesServerCallback.cs#L72-L84), as it uses [SerializableReferenceLocation](https://github.com/dotnet/roslyn/blob/a65653a77b2862329052d84816b5fb324f8bc8bd/src/Workspaces/Core/Portable/Remote/RemoteArguments.cs#L156) which uses `SerializableSymbolUsageInfo`. With https://github.com/dotnet/roslyn/pull/43914/, we added a new [FindUsagesServerCallback](https://github.com/dotnet/roslyn/blob/0852232f315e952fee1dc63a0b374614b55c1c69/src/EditorFeatures/Core/FindUsages/IRemoteFindUsagesService.cs#L32) and switched to it for Find references serialization/deserialization. This callback does not use `SerializableSymbolUsageInfo`, hence loses the SymbolUsageInfo for "Kind" column. This change fixes this part.

Restore the 'isWriteOnly' parameter removed in previous commit, and actually set Modifiers.IsWriteOnly flag based on this parameter value. This was caught by a unit test failure.