[MEDIUM] Upgrade python-filelock to 3.20.1 for CVE-2025-68146

[archana25-ms]

Merge Checklist

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

• [x] The toolchain has been rebuilt successfully (or no changes were made to it)
• [x] The toolchain/worker package manifests are up-to-date
• [x] Any updated packages successfully build (or no packages were changed)
• [x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• [x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• [x] All package sources are available
• [x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• [x] 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)
• [x] All source files have up-to-date hashes in the *.signatures.json files
• [x] sudo make go-tidy-all and sudo make go-test-coverage pass
• [x] 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? Upgrade python-filelock to 3.20.1 for CVE-2025-68146

Duplicate of https://github.com/microsoft/azurelinux/pull/15346

Change Log

• SPECS/python-filelock/python-filelock.signatures.json
• SPECS/python-filelock/python-filelock.spec
• SPECS/python-filelock/remove-python-3.14-classifier.patch
• cgmanifest.json

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2025-68146

Test Methodology

• Pipeline build id: 1011081

Build and Test is successful