…om test package

## Summary
- Remove generated `obj` directories after publishing PowerShell test tools.
- Preserve the published `bin` outputs required to run tests.
- Prevent SDK-generated build intermediates from being copied into test-package archives.

## Reason
The coordinated binaries build's Guardian CodeSign validation reported `CodeSign.MissingSigningCert` for `Microsoft.NET.Sdk.BlazorWeb.DotNetWatch.BrowserTools.Config.js` files inside the Windows test packages. Those files are generated by `Microsoft.NET.Sdk.Web` under test-tool `obj` directories and are not intended distribution artifacts.

This cleanup is in `Publish-PSTestTools`, so it covers both `New-TestPackage` and `Compress-TestContent` consumers.

Related build: https://dev.azure.com/mscodehub/PowerShellCore/_build/results?buildId=733320

## Validation
- `build.psm1` parses with no PowerShell parser errors.
- `git diff --check` passes.
- The change is limited to four lines in `build.psm1`.

----
#### AI description  (iteration 1)
#### PR Classification
Build process cleanup: removes unnecessary build intermediates from test packages.

#### PR Summary
This PR updates `build.psm1` to remove `obj` directories from the test folder during test tool publishing, ensuring build intermediates are excluded from test packages.
- `build.psm1`: Added logic to `Publish-PSTestTools` function to recursively find and delete `obj` directories under `$PSScriptRoot/test` before completing the test package publishing process.
<!-- GitOpsUserAgent=GitOps.Apps.Server.pullrequestcopilot -->

Co-authored-by: PwshBot <pwshbot@microsoft.com>
Co-authored-by: Justin Chung <124807742+jshigetomi@users.noreply.github.com>
Co-authored-by: Dongbo Wang <dongbow@microsoft.com>

…ure Linux 4

<!-- Anything that looks like this is a comment and can't be seen after the Pull Request is created. -->
# PR Summary
<!-- Summarize your PR between here and the checklist. -->
- Remove the x64 and ARM64 Azure Linux 4 mappings for the `preview` PMC channel.
- Preserve both Azure Linux 4 mappings for the `stable` PMC channel.
- Update the packaging tests to assert that preview releases do not map to Azure Linux 4 repositories.
## PR Context
<!-- Provide a little reasoning as to why this Pull Request helps and why you have opened it. -->
PowerShell preview and RC release tags select mappings with `channel: preview`. Azure Linux 4 should not receive preview PowerShell packages, so this removes only those two routing entries from `release/v7.7.0-rc.1`; stable publication remains unchanged.
Validation:
- `Invoke-Pester` for `test/packaging/packaging.tests.ps1`: passed 22 tests, failed 0.
- PowerShell parser check for the changed test file: passed with 0 errors.
- `git diff --check`: passed.
## PR Checklist
- [x] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
  - Use the present tense and imperative mood when describing your changes
- [x] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [x] [Make sure all `.h`, `.cpp`, `.cs`, `.ps1` and `.psm1` files have the correct copyright header](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [x] This PR is ready to merge. If this PR is a work in progress, please open this as a [Draft Pull Request and mark it as Ready to Review when it is ready to merge](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-a-pull-request/about-pull-requests#draft-pull-requests).
- **[Breaking changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)**
  - [x] None
  - **OR**
  - [ ] [Experimental feature(s) needed](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/main/reference/7.5/Microsoft.PowerShell.Core/About/about_Experimental_Features.md)
    - [ ] Experimental feature name(s):
- **User-facing changes**
  - [x] Not Applicable
  - **OR**
  - [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
    - [ ] Issue filed:
- **Testing - New and feature**
  - [ ] N/A or can only be tested interactively
  - **OR**
  - [x] [Make sure you've added a new test if existing tests do not effectively test the code changed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#before-submitting)

----
#### AI description  (iteration 1)
#### PR Classification
Removal of unused/deprecated package mappings, a cleanup/configuration change to stop publishing preview packages to Azure Linux 4.

#### PR Summary
This PR removes the preview...

## Summary
- Pin both PSInfra blob publication tasks to `AzurePowerShell@5.280.3`.
- Pin the BuildInfo publication task to the same known-good task revision.

## Reason
Release build [733701](https://dev.azure.com/mscodehub/PowerShellCore/_build/results?buildId=733701) resolved `AzurePowerShell@5` to a newer task revision and all three jobs failed because `New-AzStorageContext` was unavailable. Successful release build [732392](https://dev.azure.com/mscodehub/PowerShellCore/_build/results?buildId=732392) used task revision `5.280.3`.

## Validation
- Verified exactly three task references were changed.
- `git diff --check` passed.

After merge, retry the `Make Blob Public` and `Upload BuildInfo.json` release stages; binaries and packages do not need rebuilding.

----
#### AI description  (iteration 1)
#### PR Classification
CI/build pipeline configuration change to pin a task version for release stability.

#### PR Summary
Pinned the `AzurePowerShell` task version from `@5` to `@5.280.3` across pipeline templates to ensure consistent and reproducible behavior for the v7.7.0-rc.1 publishing process.
- `release-MakeBlobPublic.yml`: Pinned two instances of the `AzurePowerShell` task to version `5.280.3`.
- `release-upload-buildinfo.yml`: Pinned the `AzurePowerShell` task to version `5.280.3`.
<!-- GitOpsUserAgent=GitOps.Apps.Server.pullrequestcopilot -->

## Summary
- Install `Az.Storage 9.7.2` from the internal `PowerShellGalleryMirror` Azure Artifacts feed in each storage-publication job.
- Explicitly import `Az.Storage 9.7.2` before invoking storage commands.
- Restore the tasks to `AzurePowerShell@5`; pinning task version `5.280.3` did not address the image dependency change.

## Reason
Release run [734624](https://dev.azure.com/mscodehub/PowerShellCore/_build/results?buildId=734624) confirmed the exact task pin was honored, but `New-AzStorageContext` remained unavailable on `PSMMS2019-Secure 29.0.0`. Successful run [732392](https://dev.azure.com/mscodehub/PowerShellCore/_build/results?buildId=732392) used image version `27.0.0`, which contained the storage module.

This change removes the release jobs' dependency on the floating image's module inventory.

## Validation
- Verified exactly three storage-publication jobs were updated.
- `git diff --check` passed.

After merge, rerun only `Make Blob Public` and `Upload BuildInfo.json`; binaries and packages do not need rebuilding.

----
#### AI description  (iteration 1)
#### PR Classification
CI/CD pipeline fix to ensure the correct `Az.Storage` module version is installed for release publishing tasks.

#### PR Summary
This PR updates release pipeline templates to explicitly install and import `Az.Storage` version 9.7.2 before executing Azure PowerShell tasks, replacing the pinned `AzurePowerShell@5.280.3` task version with `AzurePowerShell@5`.
- `release-MakeBlobPublic.yml`: Adds steps to register the PowerShell Gallery mirror repository and install `Az.Storage` 9.7.2 before blob copy tasks; imports the module explicitly in inline scripts.
- `release-upload-buildinfo.yml`: Adds similar module installation step before uploading build JSON to blob storage, and imports `Az.Storage` 9.7.2 in the inline script.
- Both files downgrade the `AzurePowerShell` task version from `5.280.3` to `5` to use the latest compatible version.
<!-- GitOpsUserAgent=GitOps.Apps.Server.pullrequestcopilot -->