[Executorch] Add simd path for op quantize

[kimishpatel]

Stack from ghstack (oldest at bottom):

• [Executorch][LLM] Use caching allocator for runner #15730
• [Executorch] Make module constructors uniform across #15729
• [Executorch] Use temp allocator for allocating scratch memory #15728
• [Executorch] Introduce caching cpu memory allocator #15611
• Reduce allocation overhead in quantized sdpa #15610
• [Executorch] Add multithreading for op_quantize #15609
• -> [Executorch] Add simd path for op quantize #15608
• [Executorch] parallelize op_choose_qparams #15607
• [Executorch][llm] Fix flakyness of quantized sdpa test #15653

Reason this doesnt directly use Vectorize class is because the equivalent APIs dont exist in Vectorize class

Differential Revision: D84962236

NOTE FOR REVIEWERS: This PR has internal Meta-specific changes or comments, please review them on Phabricator!

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

As of commit d91a0d2 with merge base aba44fd ():

NEW FAILURES - The following jobs have failed:

• pull / unittest / linux / linux-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest / macos / macos-job (gh)
  The process '/usr/bin/git' failed with exit code 128
• pull / unittest-editable / linux / linux-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest-editable / macos / macos-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe

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.