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

[mmitche]

Problem

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

Solution

Reuse commit 8c6657d, semantically adapting the original change rather than blindly cherry-picking main:

• Disable package publishing on Linux and macOS in both pipeline YAMLs with /p:Publish=false.
• Add the Windows Debug/non-Release suppression missing from this release branch. The legacy PR matrix assigns _ExtraBuildArgs per configuration; the official pipeline applies a non-Release configuration guard and forwards the argument in both Windows command paths. Windows Release keeps its existing publishing behavior.
• Preserve the branch's official product build, signing, source-build, test, diagnostic/log artifact, localization, and post-build configuration. No shared templates or product code change.

Checks:

• Added unit tests

Validation: refreshed origin/release/8.0.1xx and confirmed the existing backport is one commit ahead with no base-only commits. Parsed both YAMLs, checked every Windows and Unix build command and the Release/Debug argument assignments, and structurally compared against the refreshed base after removing only the intended publishing additions; all remaining pipeline semantics match. git diff --check passes, and the committed diff contains only the two pipeline YAMLs (+15 lines).

Limitations: static validation only; no Azure DevOps template expansion, full builds, dependency installs, or live CI retry. No unit tests added for this YAML-only backport. Unrelated local long-path checkout deletions were not touched or committed.