[ROCm][CI] Cleaning and restructuring amd-ci legacy pipeline

[AndreasKaratzas]

• Moved TODOs in an isolated section
• Moved NOTES in an isolated section
• Removed unnecessary comments
• Updated test tags with current hardware targets
• Added nightly and agent pool-specific tags
• Removed custom test template
• Removed dead code (e.g., blackwell tests) and clarified the gfx950 tests that AMD team is going to implement to match blackwell tests
• Updated blocking label
• Updated timeouts
• Ordered each test group yaml key uniformly
• Removed unnecessary tentative label

UPDATE (3/8/2026):

• Merged @tjtanaa Fusions
• Merged @Alexei-V-Ivanov-AMD Blackwell tests
• Preparing for MI250 mirrors

UPDATE (3/13/2026):

• Anticipating:
  • [CI] Split V1 Others into 3 separate jobs #37016
  • [CI] Split Distributed Tests (4 GPUs) into 3 parallel jobs #37015
• Removed redundancies:
  • Deduplicated MI250, MI325, and MI355 and now each platform is going to run tests that are checking better the platform integrity.
  • There are still some seemingly hardware-agnostic tests that all 3 platforms share but that is because they provide big coverage regarding overall platform correctness and functionality integrity.
• Brought back the tentative label as it is useful for fast testing in amd-ci signal
• Updated source file dependencies to reduce the number of tests PRs request (following @okakarpa advice)

cc @kenroche

[gemini-code-assist]

Code Review

This pull request adds the tensorizer dependency to requirements/rocm-test.txt. This change appears to be a prerequisite for enabling tensorizer-related tests within the ROCm CI pipeline. While the change itself is correct and pins the dependency version, the pull request description details a wide range of CI pipeline restructuring tasks that are not reflected in the provided file changes. To avoid confusion and maintain a clear project history, I recommend updating the pull request description to accurately match the scope of this change.

[AndreasKaratzas]

I will first run a nightly with both gfx942 and gfx950 to see if this yaml is ready to be merged. I did not use AI at all for this so I want to be sure 😅

[AndreasKaratzas]

cc @Alexei-V-Ivanov-AMD @kenroche @micah-wil

[rasmith]

This will get outdated very quickly. Is this necessary? Can this TODO information be kept elsewhere? Maybe just put the TODO someplace else and then have a link pointing to it?

[AndreasKaratzas]

Having a TODO list and updating as we optimize our CI is a good idea. So I'm thinking that it's better here.

[AndreasKaratzas]

After internal discussion, we decided to move the TODO list in an umbrella issue focused entirely on ROCm CI: #34994

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @AndreasKaratzas.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @AndreasKaratzas.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork