revert sha commit pointing to main for transformers_amd_ci_ workflows

[paulinebm]

What does this PR do?

Fixes # (issue)

Code Agent Policy

The Transformers repo is currently being overwhelmed by a large number of PRs and issue comments written by
code agents. We are currently bottlenecked by our ability to review and respond to them. As a result,
we ask that new users do not submit pure code agent PRs at this time.
You may use code agents in drafting or to help you diagnose issues. We'd also ask autonomous "OpenClaw"-like agents
not to open any PRs or issues for the moment.

PRs that appear to be fully agent-written will probably be closed without review, and we may block users who do this
repeatedly or maliciously.

This is a rapidly-evolving situation that's causing significant shockwaves in the open-source community. As a result,
this policy is likely to be updated regularly in the near future. For more information, please read CONTRIBUTING.md.

• I confirm that this is not a pure code agent PR.

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• Did you read the contributor guideline,
  Pull Request section?
• Was this discussed/approved via a Github issue or the forum? Please add a link
  to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

[Copilot]

Pull request overview

This PR updates the AMD scheduled CI caller workflows to reference the reusable workflows in huggingface/hf-workflows via the main branch instead of a pinned commit SHA, so those scheduled runs track the latest upstream workflow definitions.

Changes:

• Switch uses: huggingface/hf-workflows/...@<sha> to ...@main for AMD MI250 scheduled CI callers.
• Switch uses: huggingface/hf-workflows/...@<sha> to ...@main for AMD MI325 (ARC scale set) scheduled CI callers.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 8 comments.

File	Description
.github/workflows/self-scheduled-amd-mi325-caller.yml	Updates MI325 scheduled CI reusable-workflow references from a pinned SHA to @main.
.github/workflows/self-scheduled-amd-mi250-caller.yml	Updates MI250 scheduled CI reusable-workflow references from a pinned SHA to @main.

[Copilot]

Using a mutable ref (@main) for a reusable workflow means this scheduled CI can change behavior without any change in this repo, which hurts reproducibility and can unexpectedly break scheduled runs. Since this workflow also inherits secrets on self-hosted runners, pinning to a specific commit SHA (or a version tag) is safer and makes changes auditable.

[Copilot]

Using a mutable ref (@main) for a reusable workflow means this scheduled CI can change behavior without any change in this repo, which hurts reproducibility and can unexpectedly break scheduled runs. Since this workflow also inherits secrets on self-hosted runners, pinning to a specific commit SHA (or a version tag) is safer and makes changes auditable.

[Copilot]

Using a mutable ref (@main) for a reusable workflow means this scheduled CI can change behavior without any change in this repo, which hurts reproducibility and can unexpectedly break scheduled runs. Since this workflow also inherits secrets on self-hosted runners, pinning to a specific commit SHA (or a version tag) is safer and makes changes auditable.

[Copilot]

Using a mutable ref (@main) for a reusable workflow means this scheduled CI can change behavior without any change in this repo, which hurts reproducibility and can unexpectedly break scheduled runs. Since this workflow also inherits secrets on self-hosted runners, pinning to a specific commit SHA (or a version tag) is safer and makes changes auditable.

[Copilot]

Using a mutable ref (@main) for a reusable workflow means this scheduled CI can change behavior without any change in this repo, which hurts reproducibility and can unexpectedly break scheduled runs. Since this workflow also inherits secrets on self-hosted runners, pinning to a specific commit SHA (or a version tag) is safer and makes changes auditable.

[Copilot]

Using a mutable ref (@main) for a reusable workflow means this scheduled CI can change behavior without any change in this repo, which hurts reproducibility and can unexpectedly break scheduled runs. Since this workflow also inherits secrets on self-hosted runners, pinning to a specific commit SHA (or a version tag) is safer and makes changes auditable.

[Copilot]

Using a mutable ref (@main) for a reusable workflow means this scheduled CI can change behavior without any change in this repo, which hurts reproducibility and can unexpectedly break scheduled runs. Since this workflow also inherits secrets on self-hosted runners, pinning to a specific commit SHA (or a version tag) is safer and makes changes auditable.

[Copilot]

Using a mutable ref (@main) for a reusable workflow means this scheduled CI can change behavior without any change in this repo, which hurts reproducibility and can unexpectedly break scheduled runs. Since this workflow also inherits secrets on self-hosted runners, pinning to a specific commit SHA (or a version tag) is safer and makes changes auditable.

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.