Update src/Features/Core/Portable/ReplaceMethodWithProperty/AbstractReplaceMethodWithPropertyService.cs
Co-authored-by: NCyrusNajmabadi <cyrus.najmabadi@gmail.com>

Update src/Features/Core/Portable/ReplaceMethodWithProperty/AbstractReplaceMethodWithPropertyService.cs
Co-authored-by: NCyrusNajmabadi <cyrus.najmabadi@gmail.com>

Update src/Features/Core/Portable/ReplaceMethodWithProperty/AbstractReplaceMethodWithPropertyService.cs
Co-authored-by: NCyrusNajmabadi <cyrus.najmabadi@gmail.com>

Co-authored-by: NManish Vasani <mavasani@microsoft.com>

* Use MessagePack for ISB serialization

* DocumentHighlighting service

* Renamer, EncapsulateField, TupleToStruct services

* SymbolFinder and FindUsages services

* NavigateToSearch service

* FindUsages, References fixes

* AddImport service

* SymbolSearchUpdate service

* ExtensionMethodImportCompletion service

* DependentTypeFinder service

* GlobalNotificationDelivery service

* CodeLensReferences service

* Remove CodeAnalysis service

* Remove unused code

* Fix warnings.

* Remove unused

* Error reporting and logging

* Update StreamJsonRpc to 2.6.86-alpha

* Improve callback error handling.

* Update Watson reporting

* PR feedback

* Fix tests

* Fixes

* Remove unused field

* Rename shutdown service

* Switch diagnostic serialization from ObjectReader/Writer serializer to MessagePack

* Fix diagnostic reporting issue in ASP.NET apps

* Don't offer to generate properties or fields in the global error class

* Cleanup

1. Make the error list build and live diagnostic de-duping cancellable: This ensures that repeated builds have fast error list refresh - currently, error list refresh for later builds will wait for all de-duping to complete for prior builds, just to throw away the computed results and re-refresh the error list.
2. Link error list refresh operations to workspace's disposal token
3. Eagerly initialize the saved project diagnostics from persistent storage after solution load to improve the error list refresh perf for the first build

Work towards addressing large number of recent VS Feedback requests when user invokes an explicit build:
- https://developercommunity.visualstudio.com/content/problem/1173125/error-list-sometimes-goes-empty-after-a-build.html
- https://developercommunity.visualstudio.com/content/problem/1154411/errors-persist-in-the-error-list-even-after-fixing.html
- https://developercommunity.visualstudio.com/content/problem/1149465/error-list-doesnt-show-errors-in-167x.html
- https://developercommunity.visualstudio.com/content/problem/1142347/the-error-list-cannot-be-refreshed-in-real-time-ev.html
- https://developercommunity.visualstudio.com/content/problem/1135858/error-list-errors-are-not-removed-after-successful.html
- https://developercommunity.visualstudio.com/content/problem/1134412/failed-compilation-does-not-show-errors.html
- https://developercommunity.visualstudio.com/content/problem/1126855/compile-error-view-major-bugs.html
- https://developercommunity.visualstudio.com/content/problem/1053969/error-list-not-show.html

Changes:

- Performance
   - Refresh error list during the build, as and when we either clear diagnostics or add diagnostics from build into our in progress build state. Current implementation defers all updates to the end of the build, which has couple of disadvantages:
       - It adds to overall computuation within devenv.exe at end of the build, so it takes a longer time for error list to reach the stable state. This confuses the user into thinking error list has updated, but just has stale data.
	   - Error list shows stale results during the build and  some time after the build completes till we complete de-duplication of build and live diagnostics.
   - Avoid pre-fetching compilation for all projects everytime we de-dupe build and live diagnostics after build completes. This causes the major compute overhead from the time build completes to error list is updated (could even be a few minutes). The only reason we need the compilation for this step is to determine if an analyzer is a compilation end analyzer or not, so we can grouo the reported analyzer diagnostics into live or build-only bucket correctly. I will work on a separate follow-up change to avoid this computation completely, so we don't need to fetch compilation to determine is compilation end analyzer.

- Functional
   - Update error list's "Build + Intellisense" setting to correctly show non-stable state (i.e. `Error List...`) while the build is executing and we are de-duping build and live diagnostics after build completes. Currently, the stable state for this setting only shows non-stable when solution crawler is running. This leads to error list incorrectly showing stable state when a build completes, but we are still de-duping diagnostics and solution crawler has not yet restarted. This confuses the users into thinking error list has finished all updates and has stale diagnostics.
   - Clear diagnostics for transitive projects: When we receive ClearDiagnostics(project) callback during build for projects getting re-built as part of the build, we now clear diagnostics for that project and also for all projects that transitively depend on that project. Not clearing transitively dependent project diagnostics will lead to stale diagnostics for these dependent projects in the error list, especially when user fixes errors in the core project in the dependency chain.

Co-authored-by: NCyrusNajmabadi <cyrus.najmabadi@gmail.com>

* Brokered service

* TodoCommentService ISB

* Generate PkgDef entries

* Generate VSIX manifest assets

* Brokered services

* Error reporting

* BrokeredServiceConnection

* Enable cancellation on disconnection

* Error handling

* Remove usage of WellKnownServiceHubService for brokered services

* Semantic classification services

* Fix streaming service calls

* Propagate cancellation token to all services

* Misc

* Fixes

* Feedback

* Comments

* Dispose feedback

* RPC fixes

* Rename brokered services

* Prefix services with Microsoft.VisualStudio

* Fix

* Fix cancelation of OOP analyzer requests

Account for bulk configuration editorconfig entries for computing effective descriptor severity in IDE

Fixes #47160