Add pass to remove non-contiguous dim order from a graph.

[MartinPavella]

Summary

The second (and last) part of #20094. The pass preserves the dim order of the inputs, but internally the graph will use only the contiguous dim order.

For models exported with channels last example inputs, dim_order_clone operators will be inserted to make the inputs contiguous internally. These dim_order_clone ops can then be targeted by a solution from #20095.

Test plan

pytest backends/transforms/test/test_enforce_contiguous_dim_order.py

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 1 Unrelated Failure

As of commit 16832a4 with merge base a19d1ba ():

NEW FAILURE - The following job has failed:

• pull / unittest-buck / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 768e0430cacc7289d9759896f4706512f973d23f059b6e7ce204de0c93334228 /exec failed with exit code 3

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

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

• pull / unittest-buck / macos / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 3

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

[linux-foundation-easycla]

• ❌ - login: @MartinPavella / name: Martin Pavella. The commit (16832a4) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

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