[release/9.0.3xx] Restrict CI package publishing to Windows Release

[mmitche]

Problem

Backport #10496 to release/9.0.3xx. Multiple build legs can publish packages concurrently to the shared PackageArtifacts/BlobArtifacts containers.

Solution

Semantically adapt the publishing restriction to this release branch rather than blindly cherry-picking the main-branch patch:

• Add the previously missing Windows Debug/non-Release publishing suppression in both pipeline YAMLs, with an empty override for Windows Release.
• Append /p:Publish=false to macOS and Linux builds in both YAMLs.
• Keep existing official/product build behavior, signing, source-build settings, build/test coverage, per-leg diagnostic/log artifacts, and localization unchanged. Windows overrides follow internal build arguments so the publishing restriction wins.

Reuses existing backport commit d0e7905c585d7db9b20b149050bd5ced51347432. Only azure-pipelines-pr.yml and azure-pipelines.yml change (+15 lines).

Checks:

• Added unit tests

Pipeline-only change; no unit tests added. Refreshed origin/release/9.0.3xx and verified it remains the commit's parent. The existing local release validator, scoped to this branch, passed 96 scenarios / 388 build legs, including Release-only, Release+Debug+Checked, and Debug-only configuration lists across public/internal, PR/non-PR, pipeline-definition, and source-branch combinations. It verifies Windows Release-only publishing, unchanged build-leg coverage and all non-publishing YAML structure, and wrapper argument ordering. git diff --check passed.

Validation limitations: local YAML-expression subset only; external templates and Azure server expansion were not exercised. No dependency installs, full builds, or live CI runs/retries were performed.