Upgrades lasso to version 2.9.0

[SumitJenaHCL]

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
• [x] Ready to merge

---

Summary

What does the PR accomplish, why was it needed? Upgrades lasso to version 2.9.0

Change Log

• SPECS-EXTENDED/lasso/253e8abe7b83d4d8f3d8dd5f886a54f4e173cc28.patch
• SPECS-EXTENDED/lasso/3e6f9076e19368b29a932373955a5dccd2f3cc46.patch
• SPECS-EXTENDED/lasso/625bf7d9c11ec366c45514d5ec12ab1cdd8ce094.patch
• SPECS-EXTENDED/lasso/fix-openssl-implicit-declarations.patch
• SPECS-EXTENDED/lasso/fix-removed-xmlsec-deprecations.patch
• SPECS-EXTENDED/lasso/lasso-2.8.2-python_313.patch
• SPECS-EXTENDED/lasso/lasso-libxml2.patch
• SPECS-EXTENDED/lasso/lasso.signatures.json
• SPECS-EXTENDED/lasso/lasso.spec
• cgmanifest.json

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Local Build
• 

[sandeepkarambelkar]

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

[sandeepkarambelkar]

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

[sandeepkarambelkar]

Buddy Build failed with test failures -

https://dev.azure.com/mariner-org/mariner/_build/results?buildId=924082&view=logs&j=bac295d9-f2e0-5165-e63e-e76f383e1a27&t=11f3656e-1674-514e-6598-6d74b5d3f57a

@SumitJenaHCL can you check and fix these?

[SumitJenaHCL]

Note: One of the test fails for lasso as it needs python3.13. More info https://dev.entrouvert.org/issues/92106. This patch is supposed to fix the issue but didn't work.

[sandeepkarambelkar]

Note: One of the test fails for lasso as it needs python3.13. More info https://dev.entrouvert.org/issues/92106. This patch is supposed to fix the issue but didn't work.

Can you add patch to skip the test?

[sandeepkarambelkar]

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

[sandeepkarambelkar]

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

[sandeepkarambelkar]

Lasso still have test failures - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1010938&view=logs&j=bac295d9-f2e0-5165-e63e-e76f383e1a27&t=859205e3-cba0-55b5-b3f1-35d1c4f611a6