CI: switch hardcoded Azure scale-set runners to AWS (interim)

[amd-justchen]

CI: switch hardcoded Azure scale-set runners to AWS (interim)

Why

Multi-arch CI is moving to therock-ci-config
as the single source of truth for runner scale-set / label selection. That rollout is
still in progress, so a few workflows in this repo still hardcode the legacy Azure runner
labels.

As an interim step -- until these workflows are driven by therock-ci-config -- this PR
repoints those hardcoded Azure labels at the equivalent AWS pools that the config repo
already treats as the production default. Note the shared ci-env composite action had
already migrated its Linux default to AWS; only the Windows default was still on Azure.

Label mapping (from therock-ci-config runner-config.json)

Legacy Azure label	AWS label (interim)	Notes
azure-linux-scale-rocm	aws-linux-scale-rocm-prod	linux.default AWS pool
azure-windows-scale-rocm	aws-windows-scale-rocm-prod-mix	windows.default AWS pool (mixed EPYC pool)
azure-*-heavy*	aws-linux-scale-rocm-large	none present in this repo -- no change needed

No *-heavy* / ramdisk Azure variants exist in this repo, so the heavy -> -large
mapping did not apply.

Changes

• .github/actions/ci-env/action.yml -- windows-runner output default -> aws-windows-scale-rocm-prod-mix.
  This is the high-leverage change: the windows-runner output feeds runs-on across the
  reusable component-ci.yml (and thus all component CI), so this flips the Windows default
  fleet-wide. (linux-runner was already on aws-linux-scale-rocm-prod.)
• .github/workflows/component-ci-miopen.yml -- runs-on -> aws-linux-scale-rocm-prod
• .github/workflows/clang-tidy.yml -- runs-on -> aws-linux-scale-rocm-prod
• .github/workflows/hipdnn-superbuild-ci.yml -- Windows job runs-on -> aws-windows-scale-rocm-prod-mix;
  Linux job runs-on -> aws-linux-scale-rocm-prod

Rollback

Revert this PR (restores the azure-*-scale-rocm labels). No config-repo change is
required either way; this is purely a hardcoded-label switch pending full therock-ci-config
adoption.

[amd-justchen]

Companion PR (same interim Azure->AWS runner switch) in rocm-systems: ROCm/rocm-systems#10991

[therock-pr-bot]

❌ PR Check — Action Required

Check	Status	Details
📝 PR Description	❌ Fail	Error: PR description must reference a JIRA ID, ISSUE ID, or a GitHub closing keyword. Expected: include a JIRA ID / ISSUE ID line (separator : or -, or omitted; value may be a JIRA key, a number with/without #, or a link), OR a closing keyword + issue reference. Accepted examples: • JIRA ID : TESTAUTO-6039 • JIRA ID - #330 • JIRA ID #330 • JIRA ID (on separate line) ROCM-25757 • ISSUE ID : TESTUTO-3334 • ISSUE ID #3334 • ISSUE ID - TESTAUTO-3433 • ISSUE ID (on separate line) AIRUNTIME-2352 • ISSUE ID : https://github.com/<org_name>/<repo_name>/issues/1234 • Closes #10 • Fixes octo-org/octo-repo#100 • Resolves: #123 • #123 • https://github.com/<org_name>/<repo_name>/issues/123 Current: no valid JIRA/ISSUE/closing-keyword reference found
⛔ Forbidden Files	✅ Pass	—
🧪 Unit Test	✅ Pass	PR does not contain code files — Unit Test auto-passed
🔎 pre-commit	✅ Pass	—
🚫 Draft PR	🔜 To Be Enabled	—
🚩 Feature Flag	🔜 To Be Enabled	—
📊 Code Coverage	🔜 To Be Enabled	—

⚠️ 1 policy check(s) failed. Please address the issues above before this PR can be Reviewed.

🚫 Please fix the failed policies

• ❌ PR Description

The Not ready to Review label was added to this PR. Once all policies pass, the label is removed automatically.

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

🙋 Wish to Override Policy?

[therock-pr-bot]

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

• ❌ PR Description

The Not ready to Review label has been added to this PR.
Once all policies pass, the label will be removed automatically.