* dotnet/master: (99 commits)
  Update language feature status (#23596)
  Disallow use of 'out var' in __arglist. (#23570)
  Don't include satellite assemblies in VSIX
  Fix typo in ConsoleClassifierCS.csproj
  Update .xlf files
  Mark Samples projects as NonShipping
  Turn off loc for SyntaxVisualizerExtension.csproj
  Update .xlf files
  Use wildcards in SignToolData.json
  Conditionally reference XliffTasks
  Update list of files to sign
  Add generated XLF files
  Fix the XliffTasks version
  Disable GenerateSatelliteAssemblies target
  Enable XLF-based localization
  Update Microsoft.DiaSymReader.Native to 1.7.0 stable
  added search to Roslyn option page. (#23565)
  typo
  fix connection disconnected issue in the test. (#23241)
  Update instructions to say we formally support 15.5
  ...

Fixes #23378.
Also, preserve and adjust arguments passed to 'new T'.

Enable the production of localized resources (e.g. satellite assemblies) out of the dotnet/roslyn repo.

This includes the tooling and initial (untranslated) .xlf files, but does not consume the satellite assemblies in any way. Once the Loc team has had a chance to update the files with proper translations we will work on putting the satellite assemblies into our NuGet and Willow packages.

Don't include any satellite assemblies in
Roslyn.Compilers.Extension.vsix. We're currently generating satellite
assemblies, but until the loc team has had a chance to update the .xlf
files the contents of the satellite assemblies will be wrong.

Update Microsoft.DiaSymReader.Native to 1.7.0 stable

Currently some but not all of the Samples projects are marked `<NonShipping>true</NonShipping>`, though we don't actually ship binaries for any of them. This commit marks them all as non-shipping, which stops the build from trying to build localized resources unnecessarily.

Related to https://github.com/dotnet/roslyn/issues/23566.

We've basically forced all projects to use the SDK approach to
localization, but this project doesn't use the SDK. As a result, it
doesn't produce satellite assemblies, and the build fails when we try to
copy the non-existent files to the output directory.

For the moment, just turn off XLIFF-based localization.

Use wildcards to pull in satellite assemblies for signing, rather than
explicitly listing out the path to each one.

Only reference XliffTasks in projects that produce shipping binaries.

Add the resource assemblies to the list of files to sign.

Version `0.2.0-beta-000080` only exists on my local system; we actually want version `0.2.0-beta-000081` which is publicly available.

The standard `GenerateSatelliteAssemblies` target that ships with MSBuild uses al.exe (alink) to create satellite assemblies. However, there are a couple of things it doesn't support that we need in the dotnet/roslyn repo--see issues #23190 and #23191 for details. Instead, we want to use the `CoreGenerateSatelliteAssemblies` target from Microsoft.NET.Sdk. We've already opted in to that target, and now we need to opt out of the original `GenerateSatelliteAssemblies`. Until we can move to a copy of MSBuild that includes the change in https://github.com/Microsoft/msbuild/pull/2726 the best way to do that is to redefine the target as a no-op.

1. Add the XliffTasks package for all projects.
2. Automatically update XLF files during build on dev machines.
3. Opt-in to the .NET Core satellite assembly generation task.
4. Turn off localization for non-shipping projects by default.
5. Work around an issue in locale-neutral CTO generation.

Fix unexpected EndProject line in Roslyn.sln

Several small bug fixes related to readonly references.

* added search to Roslyn option page.

* don't implicitly and with previous result.

Merge dev15.5.x into master

Emitting `foreach` over `Span` and `ReadOnlySpan` as a `for` loop

Making sure that "in" matches exactly in method group conversions.

use full duplex stream

Quick fix for signing failures

Related to #14592