Update PowerShell to 7.6.0 in .NET 10.0 and 11.0 SDK images

[chris-peterson]

Update PowerShell to 7.6.0 in .NET 10.0 and 11.0 SDK images

Problem

The .NET 10.0 and 11.0 SDK Docker images ship PowerShell 7.6.0-preview.4. PowerShell 7.6.0 has been released as GA, so the images should use the stable
release.

Approach

Updated the version from 7.6.0-preview.4 to 7.6.0 across all SDK Dockerfiles for both .NET 10.0 and 11.0. The manifest.versions.json entry for
powershell|10.0 was updated with the new version and SHA512 hashes; the 11.0 entries inherit via variable references and required no separate changes.

All five platform-specific package hashes were recomputed from the CDN-hosted .nupkg files (Linux Alpine, Linux x64, Linux arm64, Linux arm32, Windows
x64).

Testing

• Built and tested the 10.0 noble/arm64v8 SDK image locally — Docker build succeeds (SHA512 verification passes, pwsh installs and runs)
• Verified all five package URLs return HTTP 200 from the PowerShell infrastructure CDN
• Confirmed no residual 7.6.0-preview references remain in the repository

[chris-peterson]

@dotnet-policy-service agree

[lbussell]

Hi @chris-peterson, thanks for opening a PR. This change has already been implemented in #7102. As documented in CONTRIBUTING.md, pull requests should be opened against the nightly branch.

Product/dependency changes are only made in the official images once per month to avoid introducing breaking changes and unnecessary re-builds in the middle of a .NET patch cycle. We're already planning to ship the new PowerShell versions in the next .NET release on 2026-04-14, so I'm going to close this PR.