systemd-boot-signed: add aarch64 package

[SeanDougherty]

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

This adds the signed systemd-boot package for aarch64 architecture.

Change Log

Does this affect the toolchain?

NO

Test Methodology

• tbd

[CBL-Mariner-Bot]

🚨 PR Check Failed - Critical Issues Found

Found 1 critical/error issue(s) that must be fixed.

🔍 Critical Issues Detected:

1. Missing Patch File (ERROR)
   • Patch file 'https://github.com/systemd/systemd/pull/26494.patch' is referenced in the spec but not found in the directory
   • 💡 Fix: Add the missing patch file or update the Patch reference

🤖 AI Analysis Summary:

Brief Analysis:
The changes primarily add aarch64 support and bump the package release number from 22 to 23, with corresponding updates in file paths and changelog entries. No explicit CVE patch directives are introduced.

Critical Issues Found:
• ERROR: There is a changelog entry mentioning a DNSSEC integrity patch, but no corresponding Patch directive or CVE patch file (e.g., “Patch: CVE-YYYY-XXXXX.patch”) is referenced in the spec.

Recommended Actions:
• Verify whether the DNSSEC-related security fix is applied upstream or if an internal patch file is missing—if internal, add a properly numbered Patch directive referencing the patch file.
• Ensure that any future CVE fixes are documented with explicit CVE IDs and applied via %patch/%autopatch directives.
• Double-check version synchronization between spec fields and changelog entries.

---

📋 For detailed analysis and recommendations, check the Azure DevOps pipeline logs.