Add broadcast semantics to quantized ops.

[hsharma35]

Summary: Update quantized op implementation to allow broadcast semantics.

Differential Revision: D89308070

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 1 Cancelled Job, 1 Unrelated Failure

As of commit 93435f9 with merge base df626bd ():

NEW FAILURE - The following job has failed:

• pull / test-openvino-linux / linux-job (gh)
  RuntimeError: Command docker exec -t b4e01baf69f65cda8e67f6583486b169dad031c3e540f1a9b6da10e79d423f53 /exec failed with exit code 1

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

• periodic (gh)

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / android / run-emulator (gh) (#16137)
  Timeout waiting for emulator to boot.

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

[meta-codesync]

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

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