Walk transparent ops when extracting input quant params

[ethansfng]

Summary:
extract_input_quant_params_from_graph (used by QuantizedInputWrapper to dequantize pre-quantized inputs) only matched a quantize_per_tensor placed directly on the input placeholder. Inputs that pass through a shape-only op first -- an nhwc permute, or a patchify reshape -- defeated it, so callers had to pre-compute the quant params themselves.

Walk from each input placeholder through a chain of transparent ops (view/reshape/permute/transpose/slice/to/...) to the first quantize_per_tensor, so QuantizedInputWrapper(module, input_names) resolves those inputs automatically. Backward compatible (a quantize directly on the placeholder is just a zero-hop walk) and subsumes the narrower extract_quant_params_through_permute.

Differential Revision: D107922730

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ No Failures

As of commit e9b1f53 with merge base dc55469 ():
💚 Looks good so far! There are no failures yet. 💚

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

[meta-codesync]

@ethansfng has exported this pull request. If you are a Meta employee, you can view the originating Diff in D107922730.

[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.