Backport of #26398 to release/v7.4

Triggered by @TravisEz13 on behalf of @TravisEz13

Original CL Label: CL-BuildPackaging

/cc @PowerShell/powershell-maintainers

Impact

Tooling Impact

• Required tooling change

Improves ADO (Azure DevOps) package build and validation for macOS across platforms. Adds better diagnostic logging for artifact uploads and moves macOS package validation tests to a more appropriate location. These improvements help troubleshoot build issues on release branches.

Regression

• Yes
• No

This is a tooling/infrastructure improvement, not fixing a regression.

Testing

Original PR verified by:

1. Running updated macOS package builds in ADO pipeline
2. Validating improved logging output during artifact uploads
3. Running relocated package validation tests
4. Confirming builds complete successfully across x64 and arm64 architectures

Backport verified by:

1. Successfully resolved merge conflicts in mac-package-build.yml
2. Build logic adapted to release/v7.4 branch structure
3. All changes preserve release branch patterns

Risk

• High
• Medium
• Low

Medium risk: Changes build/packaging infrastructure and test locations, but improvements are valuable for maintaining build health on release branch. The enhanced logging helps diagnose issues faster. Changes have been validated in master branch and adapted appropriately for v7.4.

Merge Conflicts Resolution

Summary

One file had conflicts during cherry-pick due to code structure differences between branches.

Detailed Resolutions

File: .pipelines/templates/mac-package-build.yml

• Lines: 133-151
• Conflict: Release branch had simpler single-line artifact upload; main branch added verbose logging and foreach loops
• Resolution: Accepted incoming changes from backport which add:
  • Verbose logging before package searches (Write-Verbose "Looking for ... packages...")
  • Foreach loops to upload each package file individually with verbose output
  • Better diagnostics for troubleshooting package build issues
• Rationale: The improved logging and diagnostic output are valuable for troubleshooting builds on the release branch. No functional changes to package creation, only enhanced observability.

All resolutions verified by:

• Successful cherry-pick completion
• File changes aligned with original PR intent
• No loss of release branch-specific code patterns