[Executorch][Export][4/N] Add edge program transform stage which runs after to_edge() stage

[abhinaykukkadapu]

Stack from ghstack (oldest at bottom):

• [Executorch][Export][5/N] Remove portable lib dependency in et/export #16130
• -> [Executorch][Export][4/N] Add edge program transform stage which runs after to_edge() stage #16129
• [Executorch][Export][3/N] Add timing information to all the stages for debugging #16128
• [Executorch][Export][2/N] Add getter utils to help with getting the artifacts easily #16127
• [Executorch][Export][1/n] Add exported program and GraphModule as inputs, validation and tests #16126

Add new edge program transform stage that runs after to_edge() stage. This provides a dedicated stage for applying edge-specific transformations and passes, separating them from the general to_edge, to_backend stages.

Differential Revision: D87576717

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 11 New Failures, 1 Unrelated Failure

As of commit 95f133c with merge base 53c6ad2 ():

NEW FAILURES - The following jobs have failed:

• Build Presets / apple (llm) / build (gh)
  The process '/opt/homebrew/bin/git' failed with exit code 128
• Test CUDA Builds / check-all-cuda-builds (gh)
  Process completed with exit code 1.
• Test CUDA Builds / export-model-cuda-artifact (google, gemma-3-4b-it, non-quantized) / linux-job (gh)
  RuntimeError: Command docker exec -t 719c652f61092e9dd2011a0b1a6839b79314d6019ec18fbc4a49e83d5a9b43f6 /exec failed with exit code 1
• Test CUDA Builds / export-model-cuda-artifact (google, gemma-3-4b-it, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t 7d9f9f05eff70c202cff43a669d9ebca8cf812b03233145cc904e7b90c6d6923 /exec failed with exit code 1
• Test CUDA Builds / export-model-cuda-artifact (openai, whisper-large-v3-turbo, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t c5fd212dacc67acf637323e5a807937975367e90f32c009ec8040734146522e0 /exec failed with exit code 1
• Test CUDA Builds / export-model-cuda-artifact (openai, whisper-large-v3-turbo, quantized-int4-weight-only) / linux-job (gh)
  RuntimeError: Command docker exec -t b40f8acd2559d54b77055afc5d94450112bd00988d47bc72b56eb3be87556243 /exec failed with exit code 1
• Test CUDA Builds / export-model-cuda-artifact (openai, whisper-small, non-quantized) / linux-job (gh)
  RuntimeError: Command docker exec -t a96fc38d46b702ae1680aa4b83838fd153dc110a6e1eee9d29b45e1d0ae13c59 /exec failed with exit code 1
• Test CUDA Builds / export-model-cuda-artifact (openai, whisper-small, quantized-int4-weight-only) / linux-job (gh)
  RuntimeError: Command docker exec -t 8d53341360a6d856bfe9709f85962c70162600103e45c3505106b36180bde8e3 /exec failed with exit code 1
• Test CUDA Builds / test-executorch-cuda-build-12.6 / linux-job (gh)
  RuntimeError: Command docker exec -t 6c4c444d09484fce5c89c79549161d6921db328d66d98519ffd55512613b498c /exec failed with exit code 1
• Test CUDA Builds / test-models-cuda (add_mul) / linux-job (gh)
  RuntimeError: Command docker exec -t fcfcad302c086c4c9cec7e81f7e008fb36d4becbbe06412dc1ffb4becbae0ddc /exec failed with exit code 1
• Test CUDA Builds / test-models-cuda (conv1d) / linux-job (gh)
  RuntimeError: Command docker exec -t c5d35ea1e352733f41d16954fff1069f1e1374020503b228be3e2945816a726b /exec failed with exit code 1

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / android / run-emulator (gh) (#16137)
  Timeout waiting for emulator to boot.

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.