* Add InteractiveHost as a NuGet package

* Make InteractiveWindow a package dependency

* Update InteractiveWindow version to 2.8.0

* Add missing package dependencies

Roslyn.Compilers.VisualBasic.Test.Utilities.Desktop incorrectly added in a70cdce6
VBCSCompilerPortable removed in b2bd77b0
Microsoft.CodeAnalysis.CompilerServer removed in b00224e7
Roslyn.VisualStudio.Test.Utilities.Next renamed in e0e16d7a
Microsoft.CodeAnalysis.Scripting.Destkop.UnitTests never existed (typo)
Roslyn.DebuggerVisualizers removed in d7e49395
Microsoft.VisualStudio.LanguageServices.VisualBasic.UnitTests never existed (typo in 7ab3b776)
Roslyn.Services.Editor.CSharp.UnitTests2 renamed in bb1f97b6

See #35076

* Remove InteractiveHost dependency from nuget packages

* Fix Newtonsoft.Json ambiguity

* 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

* 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

I am removing our explicit references to Microsoft.VisualStudio.Imaging
and Microsoft.VisualStudio.Utilities; both of these are carried along
in references to Shell.15.0, and trying to state them explicitly just
results in package downgrade warnings.

Our unofficial packages don't correctly pull in some DesignTime
dependencies (since they always create packages without any
dependencies), but this caused issues once we moved to AsyncPackage
since there's new PIA types being involved. For now, to sort this out
just move back to the official packages which just do the right thing
to start.

As a part of this, I also move us to the official
Microsoft.VisualStudio.SDK.EmbedInteropTypes package; we had our own
clone of the code but it wasn't covering all the assemblies that we
now need to embed as well.

We pick up these references from EditorFeatures.csproj, so no reason
to restate.

Moving up to EditorFeatures.Wpf for now. It could potentially go higher
if we determine this is a Visual Studio-only thing, but for now it's
unclear where it will ultimately land.

Fixes dotnet/roslyn#23184.

This depends on VS APIs that we don't have open source yet, and we
don't need the feature for now in VS for Mac.

Fixes dotnet/roslyn#23192.

This lets us remove many stated dependencies on
Microsoft.VisualStudio.Text.Internal and dependency on
Microsoft.VisualStudio.Platform.VSEditor.Interop. Both
is a stated dependency of Microsoft.VisualStudio.Platform.VSEditor
which means we don't get any benefit for trying to state it -- and it's
actually hard since it has a different version anyways.

It already had access to EditorFeatures non-WPF, and so this isn't
granting access to anything it didn't already have access to.

This removes WPF and XML references.

This is a really ugly refactoring that removes the WPF APIs from
IDeferredQuickInfoContent and adds a service in EditorFeatures.Wpf that
converts from them to WPF elements. It's a straightforward refactoring
and everything still works, but it's not pretty at all.

EventHookup also worked with QuickInfo directly, and thus had to be
moved out of CSharpEditorFeatures. There isn't a CSharp-specific
EditorFeatures.Wpf assembly, so it's going into the Visual Studio layer
for now.

This is our abstraction for showing dialogs, so the WPF implementation
needs to depend on WPF.

Our presenter depends on the VS completion APIs (which aren't currently
implemented in a cross-platform way) and also depends on creating WPF
elements for tooltips, which means it can't live in EditorFeatures.Wpf
for now.

Unfortunately the tagger exposes "LineSeparatorTag" which itself exposes
WPF elements for how the tagging should be done. If it wasn't for this
mix we could have kept the tagger as a data layer in EditorFeatures
but that's not going to work.

This lets us remove a dependency in EditorFeatures.csproj on
System.Drawing.

Although this could be split out more precisely, for now we'll just
move the entire feature to the WPF layer. IEditorInlineRenameService.cs
is left behind however, as that interface is implemented by TypeScript
and other languages. For now I'm considering EditorFeatures.Wpf to be
an implementation assembly for now and so interfaces implemented
should still live in the base assembly.

In CSharpEditorFeatures and BasicEditorFeatures, there was the
implementation of IEditorInlineRenameService which had no language
specific details other than the language name the service was exported
for. I have moved those into EditorFeatures.Wpf rather than have
additional assemblies for language specific stuff, since I anticipate
that to be nearly non-existent.

This is a (currently empty) project that will contain parts of
EditorFeatures that demand the WPF surface area.