changed logger to log errors from all analyzers not just first analyzer

made diagnostic engine to verify span given to diagnostic from analyz…

Optimize fast path for "Use 'var'" code style

Update IDE Test Plan with 15.3 features

Properly push events to the OOP side so that we know when things like solution-closing happens.
Fixes #19768

Include Commit in our NuGet package

made diagnostic engine to verify span given to diagnostic from analyzers. and added explicit check in tagger for out of range

Move over to the new ITextImage platform API.

Some performance and reliability fixes around file change tracking

Switch back to the UI thread when cleaning up the solution in integration tests.

7x speedup on many SymbolFinder calls.

Do not allow ReadValue to return while a stream is still being read

Use the new valid rename field tag id in integration tests

Fix crash in VB type inferrer

Accessibility for Inline Rename in the Editor

This reverts commit 2fba37a6.

By design, when data flow analyzes local functions it does so devoid of
surrounding context and records possibly unassigned variables rather
than reporting a diagnostic. Thus, all captured variables are expected
to be marked unassigned during data flow analysis without reporting a
diagnostic.

However, reporting a diagnostic is not the only side effect of running
data flow analysis. By calling virtual methods data flow analysis
informs derived types of unassigned variables. While the diagnostic is
suppressed and recorded, currently the virtual method is still called.
This has negative consequences for region analysis, which considers
these calls as indications of variables flowing out of the given
region, which may not be the case for local functions.

This PR changes data flow analysis to only call the ReportUnassigned
virtual method if not inside a local function, excluding local functions
from all unassignment reporting.

Fixes #17165, #18347

Fixes
https://devdiv.visualstudio.com/DevDiv/_workitems?id=391624&_a=edit

- Inline Rename fields now consist of a themeable/customizable
background, foreground, and border. The border is used in High Contrast.
- Resolved and Unresolved conflict borders can now be themed &
customized.
- Resolved and Unresolved conflict borders now have different dash
styles so they are distinct from each other and regular Inline Rename
fields. The Dashboard shows a key indicating which type of conflict
corresponds to which border dash style.

Skip repl VSI tests