See #36467

See #33009

See #36468

When doing inline rename on a named type (interface, enum, or class) show a checkbox to also rename the file.

The checkbox will always show if the kind supports file rename

The checkbox will be disabled if any of the following is true:
- The type is a partial type with multiple definition locations
- The type does not currently match the file name

Extend ISyntaxFactsService to add IsTypeDeclaration
Implement file rename as part of conflict resolution for inline rename. This will allow other features to do file rename that also use the conflict resolver, all they need to do is set the correct option.

#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

* Filter out missing import fixes that would add references

* Remove superfluous IsEmpty check

* 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

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

We support configuration for boolean and enum based code style option values. The only unsupported current code style option from this fixer is specification of modifiers order, which is a custom user supplied string.

This change produced a 220MB (6.7%) allocation reduction in the scenario
described by #36158.

This enables basic support for applying top-level nullability to
parameters and the return types when generating methods.

Fixes https://github.com/dotnet/roslyn/issues/30319

* Cleanup style

* Remove BlueSquiggleForBuildDiagnostic

* TableDataSource refactoring

* Remove DiagnosticData.Workspace

* Fix workspace reference

* Simplify GetTrackingPoints

* Simplify deduplication

* EqualsModuloLocation

* Simplify navigate to

* Specialize table item

* Fix assert

* Feedback

* Dedup TryNavigateTo

* Couple of renames

Additionally, we do not mark the package reference to in Features.csproj as PrivateAsset as this leads to the assembly not getting included in the Features NuGet package and causes Omnisharp's analyzer execution to throw missing dependency assembly load errors.
Also update ExpectedDependency in DevDivInsertionFiles.csproj

Additionally, we do not mark the package reference to in Features.csproj as PrivateAsset as this leads to the assembly not getting included in the Features NuGet package and causes Omnisharp's analyzer execution to throw missing dependency assembly load errors.
Also update ExpectedDependency in DevDivInsertionFiles.csproj

Fix false positive inside catch clause (port of https://github.com/dotnet/roslyn-analyzers/pull/2501)

Address PR feedback: remove static cache, make FlowAnalysis utilities assembly load lazy and revert reference add to the FlowAnalysis assembly in Workspaces (only referenced in Features now).

(DisposableFieldsShouldBeDisposed)

We will now flag disposable creations in methods that do not escape the
method body (return value, out/ref params, assign to field/property, add
to collection, etc.). Additionally, we also flag disposable fields of
disposable types that are not disposed in the type's Dispose method.
Ported analyzers share the core dataflow analysis computation with the
analyzers in the roslyn-analyzers repo
(Microsoft.CodeAnalysis.FlowAnalysis.Utilities). This PR does not add
any code fixes. We already have a code
refactoring that offers wrapping a disposable creation within a using
statement. I am hoping to extend that to handle more cases and also
possibly convert it to a code fix in follow-up PR(s).

Fixes #33082

Fix false positive inside catch clause (port of https://github.com/dotnet/roslyn-analyzers/pull/2501)