Upgrade python-future to version 1.0.0 for python3.12 and package test fixes

[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?
python future has had a fixes go in from the latest version, mostly documentation and testing fixes. Our %check section for python-future is horribly out of date, with a couple updates after the upgrade, we are able to run the check section successfully. A few additional tests needed to be skipped for being broken on higher python versions.

Change Log

• Upgrade python-future to latest 1.0.0
• Fix up %check section in future.spec to run successfully.

Does this affect the toolchain?

NO

Test Methodology

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