Fixed CG manifest check when parsing specs with %include.

[PawelWMS]

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 (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/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

I've updated the CG manifest check in #13645 and broke parsing spec files with the %include directive. Fixing that here + adding a small clean-up of the error messages.

Does this affect the toolchain?

No.

Associated issues

• OOT Modules -> Add kernel version and release nb into release nb #13645

Test Methodology

• Local runs of the check.
• Check run for this PR for a dummy commit modifying all specs.

[Copilot]

Pull Request Overview

This PR fixes the CG manifest check when parsing specs that include the %include directive by introducing a new helper function and updating error messages.

• Introduces the chroot_rpmspec function to encapsulate chrooted rpmspec calls.
• Updates error messages and cleans up style in spec processing.

[Copilot]

[nitpick] Consider adding a function-level comment for 'chroot_rpmspec' explaining its purpose, expected arguments, behavior (including how the spec path is extracted), and error return conditions.

[Copilot]

[nitpick] Improve the error message to explicitly indicate that a valid spec file path must be provided among the arguments to 'chroot_rpmspec', which could help future debugging.