We are going to disable the DFA based IDE dispose analyzers (IDE0067, IDE0068 and IDE0069) by default as they need more performance tuning to handle large method bodies (method bodies which are 1000s of lines of code) with large control flow graphs.

#38984 has been filed to track turning these analyzers back on by default when the issue has been fixed.

This addresses the memory leak in #38330. The underlying memory leak was fixed in the FlowAnalysis utilities assembly with https://github.com/dotnet/roslyn-analyzers/pull/2795. This PR just moves to newer Roslyn Flow analysis utilities package reference with the fix.

Fixes #38330

This should fix the performance issues reported in VS feedback tickets [#672009](https://developercommunity.visualstudio.com/content/problem/672009/live-analysis-eats-up-memory-resulting-in-vs-crash.html) and [#672909](https://developercommunity.visualstudio.com/content/problem/672909/live-code-analysis-extremely-slow-and-vs-2019-cras.html)

Workaround for #32100 for Dev16.2

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

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