1. Do not flag parameters whose name has not yet been written (empty string). Fixes #36817
2. Do not flag parameters of partial method definition part. Fixes #36816

Fix couple of unit tests that started failing after #36566 merged from master to release\dev16.3-preview1

Not sure why the unit test failures were not caught by the merge PR, as these tests are failing consistently in CI for PRs targeting release\dev16.3-preview1

"Extract Interface ..." preserves banner at the top of the file

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.

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

(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

* Move IndentationService down to Feature layer.

* MOve to workspaces

* Cleanup

* Fix.

* move ISmartTokenFormatter down as well

* simplify

* Get building

* Update

* Move using inside

* Move using inside

* Move using inside

* Move using inside

* Add links

Code style based configuration tests verify all severities for the IDE code style configuration syntax. Severity based configuration tests only verifies one of the possible target severities for the dotnet_diagnostic.severity based syntax.

Add Configure severity code action to enable configuring severity of diagnostics using .editorconfig files (analyzer config documents)

Add "AdditionalDocument" type as a sub-type of TextDocument. Also introduce a "TextDocumentKind" enum to represent different kinds of text documents and refactor existing code switching on documents to now look at document kinds.

* perf tweak to run OpenFileOnly analyzers only for open files even if full solution analysis is on but run for closed files for fix all.

also made add using test to excerice OOP code properly

* addressed PR feedbacks

* added more comments

* Remove RoslynProjectType

* Remove ToolsVersion, namespace from Project tags

* Remove updating of MSBuildAllProjects

* Update BuildBoss

* Delete DeployTooolsetCompiler

The code was taken from the history (https://github.com/dotnet/roslyn/tree/4dfefe7b49c33d1d078494d52a84b16772158b11) and adapted to latest changes.

(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).