Arm backend: Remove quant_utils.py

[martinlsm]

quant_utils.py only have one public function, build_rescale, which in turn is only use by one file op_tosa_rescale.py. For this reason, move build_rescale into op_tosa_rescale.py and remove quant_utils.py.

cc @freddan80 @per @zingo @oscarandersson8218 @digantdesai

[pytorch-bot]

🔗 Helpful Links

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

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

• Long queue for ROCM runners, also B200 and XPU queueing is observed

❌ 1 New Failure, 2 Cancelled Jobs, 2 Unrelated Failures

As of commit 4db72ed with merge base c85ece4 ():

NEW FAILURE - The following job has failed:

• trunk / test-llama-runner-mac (fp32, coreml) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

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

• trunk / test-models-macos-cpu (llama, portable) / macos-job (gh)
  ##[error]The operation was canceled.
• trunk / test-models-macos-cpu (mobilebert, xnnpack-quantization-delegation) / macos-job (gh)
  ##[error]The operation was canceled.

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

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

• trunk / unittest-release / linux / linux-job (gh) (trunk failure)
  [ FAILED ] WavLoaderTest.LoadAudioDataRejectsUnsupportedFormat
• trunk / unittest-release / macos / macos-job (gh) (trunk failure)
  [ FAILED ] WavLoaderTest.LoadAudioDataRejectsUnsupportedFormat

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

[martinlsm]

@pytorchbot label ciflow/trunk

[martinlsm]

@pytorchbot label "partner: arm"

[martinlsm]

@digantdesai I think this PR needs approval from Meta since it removes a file.

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

[zingo]

@digantdesai It might be nice if you could tests this with buck2 internally?