[Bug]: Multiple artifacts failure if you re-run failed jobs after flaky tests

[freddydk]

AL-Go version

latest

Describe the issue

If a build is cancelled during tests or failing due to instability - and you subsequently re-run failed jobs (not all jobs) you will get multiple artifacts for succeeding projects and subsequent jobs cannot locate these artifacts (they get an array of artifacts). The "double" artifacts are not visible in the UI, but found when artifacts are queried. You could see this as a bug in GitHub, but we should fix this in AL-Go in a way that works, even if GitHub fixes their bug.

This build: https://github.com/Freddy-DK/DependenciesProblems/actions/runs/21090442931

Has double artifacts, see: https://api.github.com/repos/Freddy-DK/DependenciesProblems/actions/runs/21090442931/artifacts

When than downloading artifacts from prior builds for incremental builds, it fails with

throw "Multiple artifacts found with mask $artifactMask for project $projectName"

See: https://github.com/Freddy-DK/DependenciesProblems/actions/runs/21090506962/job/60661024240

Expected behavior

No failure - latest re-run build should be used

Steps to reproduce

Fork Freddy-DK/DependenciesProblems
Run CI/CD - cancel after artifacts of P1 has been published (during test analyzer)
Re-run failed jobs
Modify P0/app.json description
Build fails due to multiple artifacts

Additional context (logs, screenshots, etc.)

No response

[freddydk]

I will create a PR with a fix for this problem