Add missing Buck build targets and module exports for the cortex_m quantizer package

[psiddh]

Summary:
This diff adds missing Buck build targets and module exports for the cortex_m quantizer package

Rationale

The recent diff-train commit D89549367 added softmax support to the cortex_m backend, which introduced new quantizer files (operator_configs.py, quantization_configs.py, quantizer.py). However, the following were missing:

1. TARGETS files: No Buck build targets existed for the quantizer package, making it impossible to depend on these modules from other targets
2. init.py files: No module exports existed, preventing proper Python package imports
3. Dependency in ops/TARGETS: The ops target was missing the quantization_configs dependency needed for the operators module

Changes

• Add quantizer and quantization_configs Buck targets
• Add __init__.py with proper exports for quantizer classes and config constants
• Add missing quantization_configs dependency to ops/TARGETS
• Use appropriate build macros: runtime.python_library for xplat, python_library

Reviewed By: digantdesai

Differential Revision: D89688088

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• ROCm linux.rocm.gpu.gfx942.*.b runners switching providers

❌ 6 New Failures, 21 Pending, 14 Unrelated Failures

As of commit 685dc40 with merge base 92a8ba9 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest / macos / macos-job (gh)
  The process '/usr/bin/git' failed with exit code 1
• pull / unittest / windows / windows-job (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 1
• pull / unittest-buck / macos / macos-job (gh)
  The process '/usr/bin/git' failed with exit code 128
• pull / unittest-editable / macos / macos-job (gh)
  The process '/usr/bin/git' failed with exit code 128
• pull / unittest-editable / windows / windows-job (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 1
• Test Metal Backend / test-executorch-metal-build / macos-job (gh)
  The process '/usr/bin/git' failed with exit code 128

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

• periodic / test-models-linux (buck2, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• periodic / test-models-linux (cmake, mv3, portable, linux.2xlarge, 90) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1
• periodic / test-models-linux (cmake, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• periodic / test-models-linux (cmake, vit, portable, linux.2xlarge, 90) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• periodic / test-models-linux (cmake, vit, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• pull / test-eval_llama-wikitext-linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1
• pull / test-llama_runner_eager-linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1
• pull / test-lora-linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1
• pull / test-mediatek-models-linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1
• pull / test-models-linux (llama3_2_vision_encoder, portable, linux.4xlarge.memory) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1
• pull / test-phi-3-mini-runner-linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1
• pull / unittest / linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1
• pull / unittest-buck / linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1
• pull / unittest-editable / linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 1

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

• ⏳ pull / android / run-emulator (gh) (#16137)

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

[meta-codesync]

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

[digantdesai]

Review automatically exported from Phabricator review in Meta.

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

[psiddh]

New failures seem unrelated, landing

[zingo]

This might have cause a lot of CI problems from Etrhos-U Testing a revert PR to see if that make it work. It could be something unrelated also.

See https://hud.pytorch.org/hud/pytorch/executorch/main/1?per_page=50&name_filter=(arm-backend%7Ccortex)&useRegexFilter=true

[psiddh]

This might have cause a lot of CI problems from Etrhos-U Testing a revert PR to see if that make it work. It could be something unrelated also.

See https://hud.pytorch.org/hud/pytorch/executorch/main/1?per_page=50&name_filter=(arm-backend%7Ccortex)&useRegexFilter=true

Checking if this fwd fix : #16376 fixes the issue