* moved files

* opt-in to new "serviceOverride": true support and refactor directory structure to share json files with devdiv insertion projects

* added swr for servicehub json files.

* delete projects not needed

* moving to auto generated service.json approach

* made json file included in vsix

* generate swr file

* address PR feedbacks and remove duplications except vsix manifest

* use relative path in json file

* share duplicated string to multiple csproj

* fix swr package name

* PR feedbacks

* [WIP] first draft to move to new code lens API

* rename SemanticChangeTracker to WorkspaceChangeTracker since reference counter can change without semantic changes (such as method body change causing reference to be added or removed)

* created new dll for new code lens OOP. can't use existing VS dlls since it has more dependencies than what CodeLens can provide. we don't control code lens OOP so new dll with only depdencies required for code lens.

* fix resource id name

* pass in cancellation token on place it is missing

* ServiceHubServiceBase no longer expose Rpc directly

* address PR feedbacks

* fixed build break due to the merge

* fixed nuget version conflicts

* fixed designtime dll issue

* moved to new APIs that fix staled spans

* updated to versions suggested by editor team

* PR feedbacks

* Addressed PR feedbacks

The project which deploys ILASM tools ends up bringing two runtime
packages that have the same assets:

- runtime.win-x64.microsoft.netcore.runtime.coreclr
- runtime.win-x64.microsoft.netcore.app

Specifically assets like SOS.NetCore.dll exists at different versions in
these packages and end up getting copied twice to the output directory.
This double write ends up breaking our build (as well as basic
isolation).

The short term fix here is to no longer treat this as a code project but
instead a tools project. That eliminates the MS.NetCore.app package and
the associated double writes

Long term though the root issue needs to be addressed: making ilasm and
ildasm easier to deploy.

https://github.com/dotnet/coreclr/issues/15059

* Revert "Revert "Interactive projects refactoring (#29069)""

This reverts commit e0a8124f.

* Fix bad merge

This reverts commit 41fb51d2.

Remove Repl projects

Remove Microsoft.VisualStudio.InteractiveServices project

Remove Microsoft.CodeAnalysis.InteractiveEditorFeatures

Rename InteractiveEditorFeatures to EditorFeatures.Wpf

Remove empty resource files

Reduce InteractiveFeatures dependencies

Merge InteractiveComponents content into Roslyn.VisualStudio.Setup VSIX

Rename InteractiveFeatures to InteractiveHost

Hook fatal error handlers

Workaround warning CS1574

Exclude CreateTemplateManifestsCacheFile

Do not include satellite assemblies in DesktopHost directory

Remove VB interactive menu item

Delete VisualBasic.EditorFeatures.Wpf

Delete more unused VB interactive code

Mark Roslyn.VisualStudio.DiagnosticsWindow as a build dependency of Microsoft.VisualStudio.IntegrationTest.Setup

Fixes #33762

MonoDevelop manages their upgrade process fully independently of the
Roslyn workflow, including cases where source- or binary-breaking
changes occur. The ExternalAccess adapter assembly is unnecessary
maintenance overhead for this scenario.

This reverts commit 78d8f0fc.

* Remove RuntimeIdentifier specification

* Arcade directory layout

Added DotNet global tool for code formatting.

Tool can be run on a project, solution, or folder containing a
project or solution. Tool pulls formatting configuration from an
.editorconfig if present, otherwise formats with roslyn defaults.

* Rename target GetBuildVersion to GetVsixVersion

* Targets refactoring to align with Arcade SDK

* Remove unused property

* Use Arcade VSIX build targets

* Upload Willow VSIXes directly from VSSetup directory

* Add setup packages to Roslyn.sln

* Remove swr validation from BuildBoss

* Avoid copying CoreXT packages

* Don't delete DevDivPackages\Roslyn dir

* Upload vsixes even when the build fails

* Clean up VSIX project files

* Install VSIXes in specified order

* Do not set TargetFrameworkVersion.

* Fix parameter

* DevDivInsertion better error message

* Remove 'win' from target string

* Fix dir name

* Install Setup.Dependencies

* Default values for insertion components

* Make BuildBoss happy

* Fix VSIX path

* NGEN binaries that should have been NGEN'd

* RoboCopy returns non-zero exit code on success

* Pass OfficialBuild property to vsmanproj

* NuGet packaging

* Add missing VS package references

* Fix scripts

* Add comment on Workspace.Desktop references with PrivateAssets

* Fix Microsoft.NETCore.Compilers package

* Fix up references

* Build fixes

* Correct OutputPath for package projects

* Use NuGetRepack to force exact versions in per-build packages

Instructions can be found in the README file under src/Tools/CompilerBenchmarks.

* Enable switching bitness of interactive host

* Improve integration test error reporting

* Update integration test

By default, VS sets the first project listed in the solution as the default project. This saves new contributors from having to manually set the default project.