[Executorch] Use temp allocator for allocating scratch memory

[kimishpatel]

Stack from ghstack (oldest at bottom):

• [Executorch][LLM] Use caching allocator for runner #15656
• [Executorch] Make module constructors uniform across #15655
• -> [Executorch] Use temp allocator for allocating scratch memory #15654
• [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

This allows us to leverage temp memory allocator and if that allocator is caching allocator it reduces the allocaiton overhead.

Differential Revision: D85532076

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 Cancelled Jobs, 3 Unrelated Failures

As of commit f16910d with merge base 15a0fcd ():

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• pull / test-binary-size-linux-gcc / linux-job (gh)
• pull / test-setup-linux-gcc / linux-job (gh)

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-openvino-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest / windows / windows-job (gh) (trunk failure)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq

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.