Update AQAvit results verification process

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](https://github.com/adoptium/ci-jenkins-pipelines/pull/1027) the verification can be greatly simplified.

- No need to generate url per os, arch
- [No need to download per os_arch](https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/tapVerification/aqaTap.sh#L69-L89) 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

Start with buildenv/jenkins/tapVerification/tapVerification.groovy and aqaTap.sh, then compare their parameters and download logic with the release configuration in ci-jenkins-pipelines. Review the related issue #5242 and the referenced release Groovy and defaults.json entries. Done means verification uses the provisioned per-release results without per-platform URLs, downloads, or manually supplied PLATFORM and TARGETS.

Written by the indexing model from the issue text.