ci(jax): drop hardcoded Google DNS from wheel test containers

[amd-shiraz]

Summary

• Remove --dns 8.8.8.8 and --dns 8.8.4.4 from the Linux JAX wheel test container options.
• Drop the related DNS workaround comments / Root cause analysis for DNS resolution failures (cloudfront URL) #3014 TODO now that the flags are gone.

These were a CloudFront/runner DNS workaround and should no longer be required.

Test plan

• Confirm JAX wheel test workflows still start containers without the Google DNS flags
• Confirm package/index fetches in those jobs resolve normally (no CloudFront/DNS regressions)

Made with Cursor

[therock-pr-bot]

✅ All Checks Passed — Ready for Review

Check	Status	Details
📝 PR Description	✅ Pass	—
⛔ 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	—
🤖 therock-pr-bot	✅ Pass	—

🎉 All checks passed! This PR is ready for review.

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

🙋 Wish to Override Policy?

[therock-pr-bot]

🎉 All checks passed! This PR is ready for review.

[ScottTodd]

The test_multi_arch_linux_jax_wheels.yml workflow should run as part of CI (e.g. https://github.com/ROCm/TheRock/actions/runs/33190869165/job/98953040597), so we could wait for signal before merge.

We can also trigger https://github.com/ROCm/TheRock/actions/workflows/test_multi_arch_linux_jax_wheels.yml with workflow_dispatch from this users/shiraz.ali/remove_dns_entry branch with the inputs from a job like that (https://github.com/ROCm/TheRock/actions/runs/33190869165/job/98953040597#step:1:22) to jump straight to the tests without waiting for builds to run.