Updates for aqafer workflow

Relating to the discussion in the [Feb 22 AQAvit meeting](https://github.com/adoptium/aqa-tests/issues/4321) raised by @joe-braley, around [run-aqa](https://github.com/adoptium/run-aqa) and [aqafer](https://github.com/smlambert/aqafer) workflows, this issue is to further discuss and decide on ways to improve our Github actions and workflows (specifically the ones related to [AQAvit verification](https://adoptium.net/docs/aqavit-verification/)).

Under discussion:
- moving aqafer workflow files to the Adoptium Github org, could be sufficient to move them to this aqa-tests repository)
- co-locating this workflow in this repository would also facilitate access to some of the convenience scripts added to verify the contents of the TAP artifacts ([aqaTap.sh](https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/tapVerification/aqaTap.sh) added via https://github.com/adoptium/aqa-tests/pull/4285, could be reorganized under /[scripts](https://github.com/adoptium/aqa-tests/tree/master/scripts) directory)
- add support for optionally using internal Github runners (pool of machines)
- this potentially implies the need for a naming convention for runners used in the workflow
- ensure we utilize 'run in parallel' support (and likely enhance how this is done in run-aqa)
- documentation around opinionated/preferred ways to hook together workflows (and how to pass artifacts along to another workflow)

Joe has been working on some of these items in a [MSFT fork](https://github.com/microsoft/aqafer), where some of the work can continue (then we make the plan to move it into the Adoptium organization as per the discussion point above).

Start with the Feb 22 AQAvit meeting discussion in issue #4321 and review the aqafer work in the Microsoft fork. Read the existing workflow files and buildenv/jenkins/tapVerification/aqaTap.sh, along with the proposed scripts location. Done requires an agreed plan for workflow placement, runners, parallel execution, artifact passing, and documentation.

Written by the indexing model from the issue text.