Rustup override workflow script

[benalleng]

As some may have noticed I have been slamming my head against the wall trying to get our macos workflow working past this problem https://github.com/payjoin/rust-payjoin/actions/runs/17126953983/job/48580858265#step:6:450 but I found this recent issue rust-lang/rust#145699 but that hinges on a certain version of rust being run specifically 1.90.0 which transitions this runner to a teir 2 runner. However we should be using 1.85.0, this ensures we are forcing the rust version on our script.

Pull Request Checklist

Please confirm the following before requesting review:

• A human has reviewed every single line of this code before opening the PR (no auto-generated, unreviewed LLM/robot submissions).
• I have read CONTRIBUTING.md and rebased my branch to produce hygienic commits.

[coveralls]

Pull Request Test Coverage Report for Build 17131127396

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 86.529%

---

Totals
Change from base Build 17129145427:	0.0%
Covered Lines:	7862
Relevant Lines:	9086

---

💛 - Coveralls

[spacebear21]

Do you know when this issue originated? It didn't seem to be a problem in #876

[benalleng]

I honestly think it started just last night, I actually got some runs past this point. https://github.com/payjoin/rust-payjoin/actions/runs/17114371915

[benalleng]

rate limited 🤦‍♂️

[spacebear21]

I see...

Shouldn't the github workflow ensure 1.85 is used? We shouldn't have to update the cargo commands themselves, see e.g. the payjoin/contrib scripts

[spacebear21]

We may need this override in dart and python files due to rust-toolchain.toml having been added recently

env:
  # Override the value from the rust-toolchain file
  # This is necessary because even though the correct toolchain
  # is explicitly specified for the rust-toolchain action,
  # rustup honors the rust-toolchain file over the default
  RUSTUP_TOOLCHAIN: ${{ matrix.rust }}

[DanGould]

Rate limited on CI? I don't think testing python on every version and os is necessary. We can prune down to one. Have never seen it fail on one OS and we don't even have a production impl depending on python.

[benalleng]

Think we should just use python 3.12 to keep mac and linux the same?

[spacebear21]

Pushed a fix here #986

[benalleng]

superseded by #986