Revert "Fix KeyError in InsertIOQDQ pass for LLM quantization"

[metascroy]

Reverts #17194

Many QNN trunk jobs started failing after this PR was merged. Testing revert to see if that fixes issue.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/17385

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 1 Cancelled Job, 3 Pending, 2 Unrelated Failures

As of commit 9831c30 with merge base eb888f8 ():

NEW FAILURES - The following jobs have failed:

• trunk / test-mcu-cortex-m-backend / linux-job (gh)
  RuntimeError: Command docker exec -t 75968fb1c9545c8367f47515aa9cefd224af2cd6b4faff1bf4723045ee67419c /exec failed with exit code 1
• trunk / test-static-llama-qnn-eval-linux (baseline, 62) / linux-job (gh)
  RuntimeError: Command docker exec -t 4cdc8b8f405d0db512250f4bb83e8468e6da78239e6587b2335a34da5b920d8e /exec failed with exit code 1

CANCELLED JOB - The following job was cancelled. Please retry:

• periodic / test-models-linux (cmake, mv3, portable, linux.2xlarge, 90) / linux-job (gh)

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• Test CUDA Builds / export-model-cuda-artifact (openai, whisper-large-v3-turbo, quantized-int4-tile-packed) / linux-job (gh) (matched linux rule in flaky-rules.json)
  Error response from daemon: Head "https://registry-1.docker.io/v2/pytorch/almalinux-builder/manifests/cuda12.6": received unexpected HTTP status: 500 Internal Server Error
• Test CUDA Builds / export-model-cuda-artifact (openai, whisper-large-v3-turbo, quantized-int4-weight-only) / linux-job (gh) (matched linux rule in flaky-rules.json)
  Error response from daemon: Head "https://registry-1.docker.io/v2/pytorch/almalinux-builder/manifests/cuda12.6": received unexpected HTTP status: 500 Internal Server Error

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[metascroy]

The revert is fixing many of the broken tests, so I will proceed with land. cc @cccclai @mohammed-saalim