Promote cjose/freeradius/ipcalc pacakages to core

[suneelyadava]

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

What does the PR accomplish, why was it needed?

This PR promote pacakages from SPECS-EXTENDED to SPECS to fix customer issue https://microsoft.visualstudio.com/OS/_workitems/edit/58301574.

Change Log

• cjose promoted to core
• freeradius promoted to core
• ipcalc promoted to core

Does this affect the toolchain?

NO

Test Methodology

• Pipeline build id: 906190

[CBL-Mariner-Bot]

✅ PR Check Passed

No critical issues detected in spec file changes.

🤖 AI Analysis Summary:

Brief Analysis:
These changes primarily promote packages from SPECS-EXTENDED to SPECS with an increase in the Release numbers for cjose, freeradius, and ipcalc. No new CVE patch files were added, and the changelog notes that CVE-2023-37464 was resolved upstream in cjose.

Critical Issues Found:
• No ERROR/CRITICAL security issues detected in these changes.

Recommended Actions:
• Verify that the upstream fix for CVE-2023-37464 is correctly incorporated in cjose 0.6.2.2.
• Confirm that all migrated patch files (from extended to core) are referenced and applied as expected in the spec files for other packages.
• Maintain consistency in changelog entries and ensure any future CVE fixes include explicit patch references if not upstream integrated.

---

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

[suneelyadava]

https://dev.azure.com/mariner-org/mariner/_build/results?buildId=906190&view=results

[suneelyadava]

https://brave-ocean-0baeae310.5.azurestaticapps.net/#/build-tracker?buildNumber=3.0.20250821-suneel-906190&environment=Development