chore: Upgrade rustc to 1.93.1

[michael-weigelt]

No description provided.

[github-actions]

Run URL: https://github.com/dfinity/ic/actions/runs/22755419768

New container images with tag: a72bab43cf0ba5a4de20cacc82247b38c64a779ace23157d0aa200d3af7c41d1
ic-build: sha256:0a0cff0b12c7586c2f312c739176924edf0c9e71df92f382eba836913da9f1c6
ic-dev: sha256:a98782800df599b3d1501f0da9fbe1dff7a8a401a86c0371eaab7ae0503d3696

[basvandijk]

I'm surprised you didn't need to upgrade rules_rust for this. But I guess if it works it works.

[venkkatesh-sekar]

This might be the smallest toolchain upgrade PR!!

[github-actions]

This pull request changes code owned by the Governance team. Therefore, make sure that
you have considered the following (for Governance-owned code):

1. Update unreleased_changelog.md (if there are behavior changes, even if they are
   non-breaking).

2. Are there BREAKING changes?

3. Is a data migration needed?

4. Security review?

How to Satisfy This Automatic Review

1. Go to the bottom of the pull request page.

2. Look for where it says this bot is requesting changes.

3. Click the three dots to the right.

4. Select "Dismiss review".

5. In the text entry box, respond to each of the numbered items in the previous
   section, declare one of the following:

• Done.

• $REASON_WHY_NO_NEED. E.g. for unreleased_changelog.md, "No
  canister behavior changes.", or for item 2, "Existing APIs
  behave as before.".

Brief Guide to "Externally Visible" Changes

"Externally visible behavior change" is very often due to some NEW canister API.

Changes to EXISTING APIs are more likely to be "breaking".

If these changes are breaking, make sure that clients know how to migrate, how to
maintain their continuity of operations.

If your changes are behind a feature flag, then, do NOT add entrie(s) to
unreleased_changelog.md in this PR! But rather, add entrie(s) later, in the PR
that enables these changes in production.

Reference(s)

For a more comprehensive checklist, see here.

GOVERNANCE_CHECKLIST_REMINDER_DEDUP

[jasonz-dfinity]

LGTM for rs/registry and rs/nervous_system

[kpop-dfinity]

LGTM

Also, wanted to point out that the PR number (9113) is an anagram of the version you're updating rust to (1.93.1), good timing :P

this is a version upgrade with no semantic changes

[michael-weigelt]

Seems like the build determinism issues are gone in this version, @nmattia