Merge release/dev17.10 to release/dev17.11

[dotnet-bot]

This is an automatically generated pull request from release/dev17.10 into release/dev17.11.

Once all conflicts are resolved and all the tests pass, you are free to merge the pull request. 🐯

Troubleshooting conflicts

Identify authors of changes which introduced merge conflicts

Scroll to the bottom, then for each file containing conflicts copy its path into the following searches:

• https://github.com/dotnet/roslyn/find/release/dev17.10
• https://github.com/dotnet/roslyn/find/release/dev17.11

Usually the most recent change to a file between the two branches is considered to have introduced the conflicts, but sometimes it will be necessary to look for the conflicting lines and check the blame in each branch. Generally the author whose change introduced the conflicts should pull down this PR, fix the conflicts locally, then push up a commit resolving the conflicts.

Resolve merge conflicts using your local repo

Sometimes merge conflicts may be present on GitHub but merging locally will work without conflicts. This is due to differences between the merge algorithm used in local git versus the one used by GitHub.

git fetch --all
git checkout -t upstream/merges/release/dev17.10-to-release/dev17.11
git reset --hard upstream/release/dev17.11
git merge upstream/release/dev17.10
# Fix merge conflicts
git commit
git push upstream merges/release/dev17.10-to-release/dev17.11 --force

[dotnet-bot]

⚠ This PR has merge conflicts. @Cosifne

[dotnet-policy-service]

Auto-approval

[jjonescz]

@dibarbet can you resolve the conflicts in IDE files here? Thanks.

[dibarbet]

@dibarbet can you resolve the conflicts in IDE files here? Thanks.

@jjonescz addressed. there were a ton of conflicts in the src/Compilers/CSharp/Portable/PublicAPI.Unshipped.txt and src/Compilers/Core/Portable/PublicAPI.Unshipped.txt files. I did my best to resolve them, but please take a look to make sure it accurately reflects what you want shipped.

[dibarbet]

Source build is complaining about new prebuilts

/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24270.3/tools/SourceBuild/AfterSourceBuild.proj(81,5): error : 5 new pre-builts discovered! Detailed usage report can be found at /__w/1/s/artifacts/sb/prebuilt-report/baseline-comparison.xml.
/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24270.3/tools/SourceBuild/AfterSourceBuild.proj(81,5): error : See https://aka.ms/dotnet/prebuilts for guidance on what pre-builts are and how to eliminate them.
/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24270.3/tools/SourceBuild/AfterSourceBuild.proj(81,5): error : Package IDs are:
/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24270.3/tools/SourceBuild/AfterSourceBuild.proj(81,5): error : Microsoft.Build.17.3.4
/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24270.3/tools/SourceBuild/AfterSourceBuild.proj(81,5): error : Microsoft.Build.Framework.17.3.4
/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24270.3/tools/SourceBuild/AfterSourceBuild.proj(81,5): error : Microsoft.Build.Tasks.Core.17.3.4
/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24270.3/tools/SourceBuild/AfterSourceBuild.proj(81,5): error : Microsoft.Build.Utilities.Core.17.3.4
/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24270.3/tools/SourceBuild/AfterSourceBuild.proj(81,5): error : Microsoft.NET.StringTools.17.3.4

which were added in #73283 . However source build passed there. @marcpopMSFT any ideas on why source build is broken here?

[MichaelSimons]

@dibarbet - The source-build-reference-packages dependency needs to be updated to the latest version which contains this version.