Fix ptest failure in rng-tools

[BinduSri-6522866]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Fix ptest failure in rng-tools:

• Previously, rng-tools package builds, and in %check only rngtestjitter.sh fails. The other two tests, rngtestzero.sh and rngtesturandom.sh, run successfully.
• In tests/rngtestjitter.sh, the command uses -O jitter:use_aes:1, which shows that this test specifically depends on jitter entropy support.
  ../rngd -f -o /dev/stdout -x hwrng -x rdrand -x tpm -O jitter:use_aes:1 $TIMEOUT | ../rngtest -c 100 --pipe > /dev/null
• The code shows that jitter test needs the jitterentropy library. I checked in the Docker environment, and there is no jitter package, no jitterentropy.h file, and no jitter library available. So, this support is missing in Azure Linux 3.0
• Tested "rngtestjitter.sh" by vendoring "jitterentropy-library" and rebuilding "rng-tools" with jitter support enabled. The package builds successfully and the binary contains jitter support strings, but the jitter entropy source still does not become available at runtime in the Azure Linux 3.0 build environment.
  Even when all other entropy sources (hwrng, rdrand, tpm, pkcs11, rtlsdr) are explicitly disabled, rngd reports that it cannot open any entropy source.
• Hence, skipped the rngtesturandom.sh test.

Change Log

• ../SPECS/rng-tools/rng-tools.spec

Does this affect the toolchain?

NO

Test Methodology

• Local Build:
  rng-tools-6.16-1.azl3.src.rpm.log
  rng-tools-6.16-1.azl3.src.rpm.test.log