Allow ReleaseConfigs artifact publish to continue on job rerun

[Copilot]

Azure DevOps pipeline artifacts are immutable, so rerunning a publish-build-assets job fails with Artifact ReleaseConfigs already exists for build ... — the artifact was published by the first attempt.

Changes

eng/common/core-templates/job/publish-build-assets.yml:

• Publish ReleaseConfigs Artifact — pass continueOnError: true through the args object. A rerun proceeds past the already-exists error, while still publishing normally if the first attempt failed before this step.
• Create ReleaseConfigs Artifact — first line now uses Set-Content instead of Add-Content, so ReleaseConfigs.txt is recreated rather than appended when a retry lands on a reused workspace. Three-line format unchanged.

           displayName: Publish ReleaseConfigs Artifact
           targetPath: '$(Build.StagingDirectory)/ReleaseConfigs'
           artifactName: ReleaseConfigs
+          continueOnError: true
           retryCountOnTaskFailure: 10 # for any files being locked

Notes

• Artifact name is intentionally left as ReleaseConfigs (no $(System.JobAttempt) suffix) — downstream jobs download that stable name.
• Scoped to this step only; the generic publish-pipeline-artifacts.yml templates are untouched. Both the standard and 1ES implementations already forward continueOnError, so no changes were needed there.

To double check:

• The right tests are in and the right validation has happened. Guidance: https://github.com/dotnet/arcade/blob/main/Documentation/Validation.md

[Copilot]

Copilot wasn't able to review any files in this pull request.

[Copilot]

🟢 Approval recommended

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0 new
• Review effort level: Lite

[akoeplinger]

I think we'll hit the same issue for "Publish Merged Manifest" above.

I wonder if we could skip those tasks by checking whether eq(variables['System.JobAttempt'], 1)