Arm backend: Merge RetraceFoldedDtypesPass into FoldAndAnnotateQParam…

[martinlsm]

The pass RetraceFoldedDtypesPass carries out extra processing after the output of FoldAndAnnotateQParamsPass, meaning that they are tightly coupled and always run in sequence.

Merge these two passes together into FoldAndAnnotateQParamsPass.

Test plan

No behavior is modified. Tests already in place are sufficient.

cc @freddan80 @per @zingo @oscarandersson8218 @digantdesai

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Cancelled Job, 3 Unrelated Failures

As of commit 7dd0f11 with merge base 7ce78c0 ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 6d90a4db729d7095809f22965b82e2a7589a1e5c5f8c53a5117d45fff15c3579 /exec failed with exit code 1
• Test Metal Backend / export-voxtral-metal-artifact / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2

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

• trunk / test-models-macos-coreml (mobilebert) / 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

• pull / unittest / linux / linux-job (gh) (trunk failure)
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)
• trunk / unittest-release / linux / linux-job (gh) (trunk failure)

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

[martinlsm]

@pytorchbot label ciflow/trunk

[martinlsm]

@pytorchbot label "partner: arm"

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

[martinlsm]

Failures look unrelated

[Sebastian-Larsson]

Unrelated CI failures