fix merge issue with release bump down for python3 libs in toolchain manifests

[sameluch]

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?
Following this merge, the release number for python3-libs went from 6 to 5 unintentionally. PR to fix the issue

Change Log

• update toolchain manifest files for fasttrack to have correct version of python3-libs

Does this affect the toolchain?

YES

Test Methodology

• PR checks

[anphel31]

LGTM, I see that the 3.0 branch version of python is still on release 5 https://github.com/microsoft/azurelinux/blob/3.0/SPECS/python3/python3.spec#L9

[CBL-Mariner-Bot]

Auto cherry-pick results:

• 3.0-dev ✅ -> Skipped

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=732853&view=results