Update AQAvit results verification process

[sophia-guo]

Current verification suppose the tap files are available per platform. With the update of provision AQAvit results per release pipeline ( could be more than one job the verification can be greatly simplified.

• No need to generate url per os, arch
• No need to download per os_arch and deal with zip or tar
• No need to manually set PLATFORM parameters https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/tapVerification/tapVerification.groovy#L6, which is defined by release groovy https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/jobs/configurations/jdk21u_release.groovy
• No need to manually set TARGETS https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/tapVerification/tapVerification.groovy#L7 ( not used at all , hardcoded in aqaTap.sh ), which is set by release default https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/defaults.json#L63-L73

related #5242

[sophia-guo]

What should be verified? Ideally, take x64Linux with release testlist "sanity.openjdk,sanity.system,extended.system,sanity.perf,sanity.functional,extended.functional",extended.openjdk,extended.perf,special.functional" as example

• all testlists corresponding tap files exist - this might be a problem. As the timebased parallel, the number of child jobs is dynamic, how could we check all child taps file are avaible( e.g, one child job failed without tap file available, how to determine the correct tap file number)
• if there are failed targets in tap file, check if there is same target of same platforms passed in release triage tap file. If no, check what is the failing testcases in that failed target, if those testcases passes in release triage tapfile ( as custom_target).