Co-Authored-By: NManish Vasani <mavasani@microsoft.com>

Co-Authored-By: NManish Vasani <mavasani@microsoft.com>

Co-Authored-By: NManish Vasani <mavasani@microsoft.com>

Co-Authored-By: NManish Vasani <mavasani@microsoft.com>

* Move "is telemetry allowed" flag to DiagnosticAnalyzerInfoCache

* Clean up DiagnosticService

* Fixes

* Remove analyzer exception telemetry reporting.

* Remove reporting analyzer exceptions from SupportedDiagnostics.

The diagnostics will be reported when the compiler runs the analyzer on the compilation.

* Remove unused parameter

* Clean up analyzer telemetry reporting.

* Test fixes

* Feedback

Follow-up to https://github.com/dotnet/roslyn/pull/40289

Workspace options should now be set with `Workspace.TryApplyChanges(Workspace.CurrentSolution.WithOptions(newOptions))`

Update src/EditorFeatures/VisualBasicTest/ConvertToInterpolatedString/ConvertConcatenationToInterpolatedStringTests.vb
Co-Authored-By: NCyrusNajmabadi <cyrus.najmabadi@gmail.com>

* Refactor tuple implementation

* Tweaks

* Address PR feedback

* Pass tuple data in constructors

* Address more feedback

* Tweak comparison

* Restore constructWithTypeParameters flag to avoid overflow

* Assert that tuple parameter matches TupleUnderlyingType somewhat

* Rename to TupleData. Address some IDE feedback

* Remaining TODO2's

* Fix last IDE test!

* Factor array comparison

* Tweak WithTupleData and EqualsIgnoringTupleUnderlyingType

* Expand a test

* Remove duplicate line

* Remove an EE test for badly formed ValueTuple type

* PR feedback from Neal

* Restore an IDE test without ValueTuple

* Rename constants

* Restore formatting

* Use embedded resources for ProximityExpressionsGetter tests

* Move breakpoint resolver down into Features

We had tests that set "use tabs" but then were working in a file of
mostly spaces. The editor behavior now is to treat this as if the
file had the "use spaces" on. I alternatively could have chosen to
disable inferrence, but then it seems we're not actually testing the
more mainline scenario of somebody having tabs in the entire file, which
seems like it's worth testing over odd mixed cases.

Closes https://github.com/dotnet/roslyn/issues/39967

This reverts a workaround added in
https://github.com/dotnet/roslyn/pull/39159
which allowed us to keep our build and integration tests on 16.3.

Completion was incorrectly inferring lambda parameter types when the lambda was passed as a named argument in a different position than the corresponding parameter. We now use the name of the named argument as a first lookup to find the matching parameter, followed by a positional match.

Fixes #40043