[automated] Merge branch 'main' => 'main-vs-deps' (#79326)I detected changes in the main branch which have not been merged yet tomain-vs-deps. I'm a robot and am configured to help you automaticallykeep main-vs-deps up to date, so I've opened this PR.This PR merges commits made on main by the following committers:* CyrusNajmabadi* jasonmalinowski## Instructions for merging from UIThis PR will not be auto-merged. When pull request checks pass, completethis PR by creating a merge commit, *not* a squash or rebase commit.<img alt="merge button instructions"src="https://i.imgur.com/GepcNJV.png" width="300" />If this repo does not allow creating merge commits from the GitHub UI,use command line instructions.## Instructions for merging via command lineRun these commands to merge this pull request from the command line.``` shgit fetchgit checkout maingit pull --ff-onlygit checkout main-vs-depsgit pull --ff-onlygit merge --no-ff main# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge# Pushing the changes to the PR branch will re-trigger PR validation.git pushhttps://github.com/dotnet/roslyn HEAD:merge/main-to-main-vs-deps```<details><summary>or if you are using SSH</summary>```git push git@github.com:dotnet/roslyn HEAD:merge/main-to-main-vs-deps```</details>After PR checks are complete push the branch```git push```## Instructions for resolving conflicts:warning: If there are merge conflicts, you will need to resolve themmanually before merging. You can do this [using GitHub][resolve-github]or using the [command line][resolve-cli].[resolve-github]:https://help.github.com/articles/resolving-a-merge-conflict-on-github/[resolve-cli]:https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/## Instructions for updating this pull requestContributors to this repo have permission update this pull request bypushing to the branch 'merge/main-to-main-vs-deps'. This can be done toresolve conflicts or make other changes to this pull request before itis merged.The provided examples assume that the remote is named 'origin'. If youhave a different remote name, please replace 'origin' with the name ofyour remote.```git fetchgit checkout -b merge/main-to-main-vs-deps origin/main-vs-depsgit pullhttps://github.com/dotnet/roslyn merge/main-to-main-vs-deps(make changes)git commit -m "Updated PR with my changes"git pushhttps://github.com/dotnet/roslyn HEAD:merge/main-to-main-vs-deps```<details>    <summary>or if you are using SSH</summary>```git fetchgit checkout -b merge/main-to-main-vs-deps origin/main-vs-depsgit pull git@github.com:dotnet/roslyn merge/main-to-main-vs-deps(make changes)git commit -m "Updated PR with my changes"git push git@github.com:dotnet/roslyn HEAD:merge/main-to-main-vs-deps```</details>Contact .NET Core Engineering (dotnet/dnceng) if you have questions orissues.Also, if this PR was generated incorrectly, help us fix it. Seehttps://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

Build Branch: refs/heads/release/dev17.14Internal ID: 20250529.5Internal VS ID: rel.d17.14-36221.01

[automated] Merge branch 'main' => 'main-vs-deps' (#79074)I detected changes in the main branch which have not been merged yet tomain-vs-deps. I'm a robot and am configured to help you automaticallykeep main-vs-deps up to date, so I've opened this PR.This PR merges commits made on main by the following committers:* davidwengier## Instructions for merging from UIThis PR will not be auto-merged. When pull request checks pass, completethis PR by creating a merge commit, *not* a squash or rebase commit.<img alt="merge button instructions"src="https://i.imgur.com/GepcNJV.png" width="300" />If this repo does not allow creating merge commits from the GitHub UI,use command line instructions.## Instructions for merging via command lineRun these commands to merge this pull request from the command line.``` shgit fetchgit checkout maingit pull --ff-onlygit checkout main-vs-depsgit pull --ff-onlygit merge --no-ff main# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge# Pushing the changes to the PR branch will re-trigger PR validation.git pushhttps://github.com/dotnet/roslyn HEAD:merge/main-to-main-vs-deps```<details><summary>or if you are using SSH</summary>```git push git@github.com:dotnet/roslyn HEAD:merge/main-to-main-vs-deps```</details>After PR checks are complete push the branch```git push```## Instructions for resolving conflicts:warning: If there are merge conflicts, you will need to resolve themmanually before merging. You can do this [using GitHub][resolve-github]or using the [command line][resolve-cli].[resolve-github]:https://help.github.com/articles/resolving-a-merge-conflict-on-github/[resolve-cli]:https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/## Instructions for updating this pull requestContributors to this repo have permission update this pull request bypushing to the branch 'merge/main-to-main-vs-deps'. This can be done toresolve conflicts or make other changes to this pull request before itis merged.The provided examples assume that the remote is named 'origin'. If youhave a different remote name, please replace 'origin' with the name ofyour remote.```git fetchgit checkout -b merge/main-to-main-vs-deps origin/main-vs-depsgit pullhttps://github.com/dotnet/roslyn merge/main-to-main-vs-deps(make changes)git commit -m "Updated PR with my changes"git pushhttps://github.com/dotnet/roslyn HEAD:merge/main-to-main-vs-deps```<details>    <summary>or if you are using SSH</summary>```git fetchgit checkout -b merge/main-to-main-vs-deps origin/main-vs-depsgit pull git@github.com:dotnet/roslyn merge/main-to-main-vs-deps(make changes)git commit -m "Updated PR with my changes"git push git@github.com:dotnet/roslyn HEAD:merge/main-to-main-vs-deps```</details>Contact .NET Core Engineering (dotnet/dnceng) if you have questions orissues.Also, if this PR was generated incorrectly, help us fix it. Seehttps://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

[automated] Merge branch 'main' => 'main-vs-deps' (#79074)I detected changes in the main branch which have not been merged yet tomain-vs-deps. I'm a robot and am configured to help you automaticallykeep main-vs-deps up to date, so I've opened this PR.This PR merges commits made on main by the following committers:* davidwengier## Instructions for merging from UIThis PR will not be auto-merged. When pull request checks pass, completethis PR by creating a merge commit, *not* a squash or rebase commit.<img alt="merge button instructions"src="https://i.imgur.com/GepcNJV.png" width="300" />If this repo does not allow creating merge commits from the GitHub UI,use command line instructions.## Instructions for merging via command lineRun these commands to merge this pull request from the command line.``` shgit fetchgit checkout maingit pull --ff-onlygit checkout main-vs-depsgit pull --ff-onlygit merge --no-ff main# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge# Pushing the changes to the PR branch will re-trigger PR validation.git pushhttps://github.com/dotnet/roslyn HEAD:merge/main-to-main-vs-deps```<details><summary>or if you are using SSH</summary>```git push git@github.com:dotnet/roslyn HEAD:merge/main-to-main-vs-deps```</details>After PR checks are complete push the branch```git push```## Instructions for resolving conflicts:warning: If there are merge conflicts, you will need to resolve themmanually before merging. You can do this [using GitHub][resolve-github]or using the [command line][resolve-cli].[resolve-github]:https://help.github.com/articles/resolving-a-merge-conflict-on-github/[resolve-cli]:https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/## Instructions for updating this pull requestContributors to this repo have permission update this pull request bypushing to the branch 'merge/main-to-main-vs-deps'. This can be done toresolve conflicts or make other changes to this pull request before itis merged.The provided examples assume that the remote is named 'origin'. If youhave a different remote name, please replace 'origin' with the name ofyour remote.```git fetchgit checkout -b merge/main-to-main-vs-deps origin/main-vs-depsgit pullhttps://github.com/dotnet/roslyn merge/main-to-main-vs-deps(make changes)git commit -m "Updated PR with my changes"git pushhttps://github.com/dotnet/roslyn HEAD:merge/main-to-main-vs-deps```<details>    <summary>or if you are using SSH</summary>```git fetchgit checkout -b merge/main-to-main-vs-deps origin/main-vs-depsgit pull git@github.com:dotnet/roslyn merge/main-to-main-vs-deps(make changes)git commit -m "Updated PR with my changes"git push git@github.com:dotnet/roslyn HEAD:merge/main-to-main-vs-deps```</details>Contact .NET Core Engineering (dotnet/dnceng) if you have questions orissues.Also, if this PR was generated incorrectly, help us fix it. Seehttps://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

Fix OOP crash issue with copilot change analysis (#78931)

Build Branch: refs/heads/release/dev17.14Internal ID: 20250529.5Internal VS ID: rel.d17.14-36203.30

Build Branch: refs/heads/release/dev17.14Internal ID: 20250429.6Internal VS ID: rel.d17.14-36202.13

Refactoring of extension methods in source packages (#78620)* Change namespace of OneOrMany and TemporaryArray to MS.CA.Collections* Cleanup Enumerable and ImmutableArray extensions* Update imports/usings

Build Branch: refs/heads/release/dev17.12Internal ID: 20250126.6Internal VS ID: rel.d17.12-36129.13

Build Branch: refs/heads/release/dev17.10Internal ID: 20250106.12Internal VS ID: rel.d17.10-36129.12