These settings are already applied by Formatting Analyzer during builds,
but might get overridden by user settings when attempting to format
documents inside the IDE. Explicitly specifying the options in
.editorconfig means the options are uniformly applied inside and outside
the IDE.

Fix an assert in unused members analyzer for newly added IReDimClause…

Add workaround to unused parameters/values analyzer for code with con…

Workaround for #31820. Issue #31821 tracks reverting this workaround once #31820 is addressed.

Add some more bail out cases for unused parameters and value assignments analyzers

Format documents in solution

Found while dogfooding latest bits

Fix the action registration for unused parameters analyzer to ensure …

Remove assumption that project names are unique

Fix 'convert to tuple' analyzer.

* Arcade SDK 1.0.0-beta.18613.10

* Keep workaround for bad Test SDK package

* Arcade 1.0.0-beta.18613.19

* Change the order of imports

* Disable SourceLink, Xliff in WPF temp projects

Enable FormattingAnalyzer

This changes the code style analyzers so that they only execute on the
build correctness leg. This means that even in the face of style errors
our build will be covered via this leg but we will also get test run
output as the other legs won't hit the style errors.

Use SetUpEditor instead of SetText

Fix the action registration for unused parameters analyzer to ensure no duplicate diagnostics are reported

Fixes #31381
This repros intermittently based on the ordering of symbol end action callbacks, so it is not possible to add a reliable regression test.

Minimize all before starting integration tests on CI

This change updates the initialization of BasicNavigationBar to match
the behavior of CSharpNavigationBar.

Fix build task on CoreClr 3.0

* Eliminate differences between Arcade and Roslyn targets

* Remove RootNamespace setting as it's overwritten by Core SDK

Bail out from unused value assignment analysis in presence of delegates passed as arguments to method invocation.

Do not report unused value assignment for VB static local assignment and unused parameter for VB Handles method parameters.

Fixes #31744

While refactoring the project system shims I assumed what we were
calling the "unique name" was actually unique. It's not, really --
you can have the same name in different solution folders. We only use
this name for hosting IVsContainedLanguage instances, and it turns out
there we were first filtering by IVsHierarchy and only using the name
to distinguish after that. This returns to that pattern.

Ensure Visual Studio has focus at the start of each new test