We were not generating a cached completion item rule for a non-preselected item in a tuple context that was also an alias context
Fixes dotnet#22002

Stop swallowing JTF exceptions

Fix completion crash in tuple in alias

…t#21890)

Previously, we supported a light-up ability where we would use the
appropriate completion APIs for Dev14 or Dev15 depending upon which
version of Visual Studio we were targeting. We no longer support such
a configuration, so we can flatten all the code and indirection back
down.

Previously, we supported a light-up ability where we would use the
appropriate Navigate To APIs for Dev14 or Dev15 depending upon which
version of Visual Studio we were targeting. We no longer support such
a configuration, so we can flatten all the code and indirection back
down.

These helpers allowed us to do lightup between Dev14 and Dev15 for some
features. We no longer support Dev14, so that is unnecessary.

This lived in EditorFeatures.Next since it depended on Dev15 features,
but EditorFeatures is now Dev15 only so we can move this.

…udio

We don't need the split anymore now that we're only supporting Dev15.

Unfortunately this required the introduction of a NuGet package that
has a namespace "Workspace" to our VS project, which meant I had to
disambiguate Workspace wherever it's used in that layer. I considered
doing an extern alias instead to disambiguate, but applying that to a
ProjectReference isn't supported. That's tracked by NuGet/Home#4989.

…ioSetup

This transfers all the VSIX contents of VisualStudioSetup.Next
back to VisualStudioSetup, making VisualStudioSetup a Dev15 VSIX again.

Fix up .gitattributes to clone .sh files with LF

* Remove context (enclosing type name) from C# parser.
* Add a test demonstrating that unicode escapes are significant to determining if a method is a ctor.
This is a prerequisite to dotnet#367

…jects

Delete .Next projects