Cadence ops: Support quantized_w8a32_linear

[DrJessop]

Summary: As titled.

Differential Revision: D84745967

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures, 5 Unrelated Failures

As of commit 0e6cd2b with merge base bd34e74 ():

NEW FAILURES - The following jobs have failed:

• Build Presets / windows (windows) / build (gh)
• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t c8e370cfd224b50112c2f1a71d2dc08ec9c86c453b97e0e0583beebd61e1de37 /exec failed with exit code 1
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t 311220939f753c85bf14d74cf52fd34012a4e6f59eb4f9cef61501c290b5d335 /exec failed with exit code 1
• Test CUDA Builds / export-voxtral-cuda-artifact / linux-job (gh)
  RuntimeError: Command docker exec -t ce2135fa2a6d393c93161dcf94f8dd01d3870ef8ceeed2d0d4257755dbca404c /exec failed with exit code 2

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / test-binary-size-linux-gcc / linux-job (gh) (trunk failure)
• pull / test-openvino-linux / linux-job (gh) (trunk failure)
• pull / test-setup-linux-gcc / linux-job (gh) (trunk failure)
• pull / unittest / linux / linux-job (gh) (trunk failure)
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)

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

[meta-codesync]

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

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