* Dont try and check tuple conversions in error cases:
- When checking an identity converison, also check for a bound tuple if the type isn't a tuple as we might have a bound tuple with an error type
- When checking a tuple conversion, don't GenerateConversion in the error case as we don't have a target type to generate against
- Update tests

* Add back constructor to ProjectExternalErrorReporter

* Add missing imports to ProjectExternalErrorReporter

#36330 tracks enabling them

* Added fsharp shims over document diagnostic analyzers

* Added shims for completion and sig help. Also added tests.

* Moved around internal files. Added shim over InlineRenameService.

* Starting shim over document highlights service. Added a better way to handle diagnostics

* Added shim for document highlights service

* Added IFSharpDocumentNavigationService

* Added IFSharpGoToDefinitionService

* Added IFSharpNavigationBarItemService

* Added IFSharpNavigateToSearchService

* Added extra glyph case

* Added FSharpGlyphTags

* Added FSharpCommentSelectionService

* Some cleanup. Added FSharpBlockStructureService

* Added some simple statics

* Finishing the last of shims

* Getting analyzers to work

* Remove folder

* Changes due to feedback

* Fixing build

* Still trying to fix build

* Fixed guid

* Fixing build again

Fixes #36315

* Filter out missing import fixes that would add references

* Remove superfluous IsEmpty check

See #30165
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/754127

* Use ref locals to simplify code flow
* Fix VB code layout

Some reference assemblies omit information about private fields. To
avoid treating structures in these assemblies as immutable, we only
consider types immutable if they contain information about one or more
private fields.

This is a workaround for issues like dotnet/standard#678.

Works around microsoft/vs-streamjsonrpc#272

* Ctor refactoring

* Renames

* Renames

* Cleanup

* ProjectExternalErrorReporter ctor

* Refactoring

* Remove dependency on VS

* Aggregation improvements

* Use ordinal comparer for project names

* Construct ProjectExternalErrorReporter lazily

* Fix off by one

* Fix issues

* Wip

* Update more pages

* Formatting

* Respond to feedback

* Add spacing to Formatting General page

* Get SVsSolution service instead of IVsSolution

* Use the correct GetService overload

this particular code path can take a long time if metadata reference hasn't created its symbols yet.

this can get really bad if we try to show code lens for something like IDispose.Dipose and it tries to create all metdata references in the solution.

since it is not cancellable, just passing by a Dipose method can cause this to occupy CPU 100% for several seconds and there is no way to make it go away.

now we pass in cancellation token so that we can bail out  sooner.

Closes #35808

RenameTrackingDiagnosticAnalyzer is the only remaining in-process
analyzer, which is tracked by #35808. Use of IInProcessAnalyzer in new
locations is not allowed.

This change allows the PerformanceSensitiveAttribute to be applied to
the method. See dotnet/csharplang#1888.

This test is flaky in legacy completion, but legacy completion is slated
for removal so the test failures were not fully investigated.

Our CI machines don't have a new enough MSBuild to support this; adding
it is tracked by https://github.com/dotnet/core-eng/issues/6424 which
is currently underway but there's no reason to hold up the larger
work on the test.

* Write Roslyn assembly version to DependentAssemblyVersions file

* Depend on GetAssemblyVersion to ensure AssemblyVersion has been calculated