add patches from fedora f40 to fix tests with new versions of openssl and python

[tobiasb-ms]

• 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

In newer versions of openssl and python, some error strings changed which breaks some tests in openvswitch. Fedora version F40 deals with this via two patch files that change how openvswitch handles these errors.

This change adds those passes to make p-tests pass consistently. Note that this is a test only change. The patches only affect tests. This package creates a lot of binaries but I spot checked a few and the old and updated binaries were identical.

Change Log

• Added patch files to properly handle openssl and python errors in openvswitch tests
• Updated license installation
• Bumped release

Does this affect the toolchain?

NO

Test Methodology

• Buddy Build Before: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1022346&view=results
• Buddy Build After: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1022473&view=results