openjdk_build_pipeline jobs can't gather all downstream test job's tapfiles

[sophia-guo]

openjdk_pipeline jobs can't gather all downstream test job's tapfiles. Take https://ci.adoptium.net/job/build-scripts/job/release-openjdk20-pipeline/5/ for example run verification https://ci.adoptium.net/view/Test_grinder/job/TAP_verification/24/console from console output some tap files are missing. Some jobs are not available now. From jobs available tap files are missing if

• test jobs result is aborted. https://ci.adoptium.net/job/build-scripts/job/jobs/job/release/job/jobs/job/jdk20/job/jdk20-release-windows-x64-temurin/5/ doesn't have extended.openjdk tapfile, the downstream job is aborted https://ci.adoptium.net/job/Test_openjdk20_hs_extended.openjdk_x86-64_windows/30/
• test jobs result is unstable. For example https://ci.adoptium.net/job/build-scripts/job/jobs/job/release/job/jobs/job/jdk20/job/jdk20-release-alpine-linux-x64-temurin/4/ doesn't have extended.openjdk tapfiles. THe downstream job is unstable https://ci.adoptium.net/job/Test_openjdk20_hs_extended.openjdk_x86-64_alpine-linux/29/

[sophia-guo]

Case 1: test jobs result is aborted.

Originally only success and unstable are considered https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/build/common/openjdk_build_pipeline.groovy#L466

[sophia-guo]

Case 2: test jobs result is unstable. Related with PR Propagate downstream build & test results for pipeline. With Propagate=true build job complete as non-successful will fail the build stepand returns null https://issues.jenkins.io/browse/JENKINS-48475?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&showAll=true. Build job has been using catchError to avoid stopping the whole build.