Arm backend: Propagate node info from quantizer to backend

[oscarandersson8218]

Use the Node meta 'custom' field to propagate information from quantizer to partitioner using a new ArmAnnotationInfo data class. This allows us to track quantized node reliably which is useful in order to track which nodes should 'fold' it's quantization parameter and which should be kept in fp when mixing integer and float in a sub-graph.

cc @freddan80 @per @zingo @digantdesai

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 9 New Failures, 4 Unrelated Failures

As of commit ce3dd25 with merge base de56c81 ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 46dbe6347535db0926b6bda96bd2740df052606ebb6e79b6245eaf7b7986f630 /exec failed with exit code 1
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t 2ef9811571694cd30158a1d430801bd384d8eedac8bdb1d007227c357108a146 /exec failed with exit code 1
• Test CUDA Builds / export-gemma3-cuda-non-quantized / linux-job (gh)
  RuntimeError: Command docker exec -t a4de32e31293caebc874bf219929cfbd83799f231edb056b19b17cb44fb48b5a /exec failed with exit code 2
• Test CUDA Builds / export-gemma3-cuda-quantized-int4-tile-packed / linux-job (gh)
  RuntimeError: Command docker exec -t 7f1c00d9ffc57f090a92bd28ee41bca7f513407973efd145d06bf1a5966e3953 /exec failed with exit code 2
• Test CUDA Builds / export-voxtral-cuda-non-quantized / linux-job (gh)
  RuntimeError: Command docker exec -t 3952f2712d81b0a83122e098f492dac73f8f0f498a0833687c523c83de7e227f /exec failed with exit code 2
• Test CUDA Builds / export-voxtral-cuda-quantized-int4-tile-packed / linux-job (gh)
  RuntimeError: Command docker exec -t 93eb1e4a4ce5e5c066b60c4123d1ae53bd783ed713b71bb151f1a9a6d0ced262 /exec failed with exit code 2
• Test CUDA Builds / export-voxtral-cuda-quantized-int4-weight-only / linux-job (gh)
  RuntimeError: Command docker exec -t 132ad43a6431973d4e0035eba826fd3e5236baaad4f52049fdff5773f598daf8 /exec failed with exit code 2
• 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
• 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

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

• pull / unittest / linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• trunk / unittest-release / linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is 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 / macos / macos-job (gh) (trunk failure)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_mv3_model
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)

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

[oscarandersson8218]

@digantdesai What are your thoughts on this conceptually?