feat: add QA testcase vagrant box definitions, scripts and examples

[tcooper]

This PR adds capability to conduct QA Testcases in semi-automated or manual fashion.

The following testcases are covered:

• QA:Testcase Mediacheck
• QA:Testcase Debranding Analysis

The style of this submission serves as an example layout for other possible QA:Testcase scenarios but is not the only style that may be submitted and/or accepted.

---

Author checklist (to be completed by original Author)

• [x] I have signed the Rocky Open Source Contributor Agreement (ROSCA).
• [x] I certify this contribution complies with all conditions of the Testing repository contributions guide
• [x] If applicable, steps and instructions have been tested to work on a real system.
• [x] I have installed pre-commit and all commits in this PR pass.
• [x] If applicable, I have GPG signed all commits and unploaded my private key to Github.

---

Rocky Testing checklist (to be completed by Rocky team)

• [x] 1st Pass (Check that contribution is good fit for project and the Testing repository is the appropriate location)
• [x] 2nd Pass (Confirm all pre-commit tests pass)
• [ ] 3nd Pass (Technical Review - check for technical correctness)

[tcooper]

No longer a draft. All packages on the debrand list for r9 pass debranding from Peridot yumrepofs local cache.

[tcooper]

Rebased to development branch to use as example with new branch protections. A single review should unblock this PR from merge.

[StackKorora]

There are a bunch of output files. Are those necessary to be in the git repo or can that folder be excluded?

[tcooper]

Output files are there as examples and are intentionally included but could be removed.

[tcooper]

Went to create new PR for the recent testing and found this PR was still unmerged. Question from @StackKorora about output files which were provided as examples. Response was they could be removed and no more discussion. Will bring up in next meeting...