upgrade rust to 1.85.0

[KavyaSree2610]

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?

• Upgrade rust to 1.85.0

Change Log

• Upgrade to 1.85.0
• Drop unnecessary patches in rust
• Remove expand-yaml-anchors tool in %check
• Remove rust-demangler tool
• Run tests as non root user in rust package
• Skip some failing ci ptests
• Build all packages which are dependent on rust

Does this affect the toolchain?

NO

Associated issues

• https://microsoft.visualstudio.com/OS/_workitems/edit/54094911

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2024-9681

Test Methodology

• Pipeline build :
• https://dev.azure.com/mariner-org/mariner/_build/results?buildId=783057&view=results (SPECS without ptests)
• https://dev.azure.com/mariner-org/mariner/_build/results?buildId=783257&view=results (SPECS-EXTENDED without ptests)
• https://dev.azure.com/mariner-org/mariner/_build/results?buildId=783058&view=results (SPECS with ptests) (this is not green because of failing arm64 ptests in flux which is happening even before upgrade)
• https://dev.azure.com/mariner-org/mariner/_build/results?buildId=783258&view=results (SPECS-EXTENDED with ptests) (this is not green because of failing ptests of dependencies of 389-ds-base

[mfrw]

Can we please skip the failing tests, so that the pipeline is green.
Let's add a link where we skip to the FreeBSD forum to clarify on why are we even skiping :)

[ms-mahuber]

As the PR progresses, can we please post up to date pipeline links for all affected packages, showing build and package tests to behave according to our findings?

[KavyaSree2610]

In retrospect, we should get to the bottom of why these patches removing tests are required before proceeding.

done with the investigation of the tests