Use pooling pattern for ArrayBuilders.

Move SyntaxFacts service down to CompilerExtensions shared project

Add OptionSet.AsAnalyzerConfigOptions

Add UnitTests for Issue #38513

Switch to an easier pooling model for pooled collections in the IDE.

Don't suggest using named arguments for implicit Index and Range indexers

* Failing tests for writing with a range starting > 0

* Fixed SourceText.Write for spans that don't start at 0

* Math.Min is redundant with CheckSubSpan

* TextSpan guarantees that Start >= 0

* TextSpan guarantees that Start <= End

* Assert is preferred over comment

Move back the ContextQuery related extensions and corresponding SyntaxFact APIs up to the shared WorkspaceExtensions project

Move ISyntaxKindsService language service in shared layer

Prohibit C# 8 index and range usage in expression trees

Enable viewing shared resx files in shared projects

Stop emitting initobj without address for default expression temp ref local

- Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.20127.9

Split `ISyntaxKindsService` into two parts:

1. `ISyntaxKinds`: Pure data query interface, which already exists in CompilerExtensions shared project and can be used by analyzers.
2. `ISyntaxKindsService`: The `ILangaugeService` implementation of `ISyntaxKinds`

Above split ensures that we can move the `ISyntaxKindsService` language service implementation down to the WorkspaceExtensions project, which in turn ensures that `GetLanguageService<ISyntaxKindsService>` will always succeed in our entire code base. This is currently not true in CodeStyle fixes layer due to the fact that the language service implementation is defined in Workspaces.csproj

Split ISyntaxFactsService into two parts:

1. `ISyntaxFacts`: Pure data interface to query about syntactic facts. This is moved to CompilerExtensions shared project and can be used by analyzers.

2. `ISyntaxFactsService`: Derives from ISyntaxFacts and ILanguageService and is present in the WorkspaceExtensions shared project. This enables Code fixes and Workspaces layer to access the same functionality via a language service, i.e. `GetLanguageService<ISyntaxFactsService>`.

Note that we cannot use a partial declaration for `ISyntaxFactsService` instead of `ISyntaxFacts`. This causes `ISyntaxFacts` to be defined in both the CodeStyle analyzer and CodeStyle fixer assembly (former imports CompilerExtensions and latter imports WorkspaceExtensions), which leads to type conflicts. We also cannot follow the approach taken for `ISyntaxKindsSevice` as it defines the second partial declaration `ISyntaxKindsSevice` which sub-types `ILanguageService` in Workspaces project, leading to the language service not being defined in CodeStyle fixer assembly, which will cause any code fix requesting `GetLanguageService<ISyntaxKindsService>` to fail. The only feasible approach for us to have the functionality available in shared analyzer layer is to split out the pure data query part of the service to a separate type, as done in this PR. I will send a follow-up PR to also split `ISyntaxKindsService` similarly. Hoepfully, these two are the only language services that are commonly used by our analyzers, and we will not require any more such splits.

Move bunch of analyzer base types and test utility types into shared …

Fixes #41682
Fixes #40326

Use GetRequiredSemanticModelAsync where appropriate

Use Arcade Roslyn compiler

Workaround for https://github.com/dotnet/project-system/issues/5925 so resx files in shared projects are visible in Solution explorer

Expose several SyntaxGenerator methods.