Arm backend: Generalize fuse_view_copy_transform_pass

[AdrianLundell]

Update the fuse_view_copy_transform_pass to check shapes rather than args to match different ways of expressing the same shape. This change makes some as_strided ops into noops which they were not previously so an additional noops check is added to fix this.

Additionally moves constants in the pass to class level to simplify overriding behavior for inheriting passes.

Note: test names as_strided_copy -> as_strided since the _copy suffix of operator names are removed in name check.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

⚠️ 1 Awaiting Approval, 3 Unrelated Failures

As of commit 21f1923 with merge base ba54389 ():

AWAITING APPROVAL - The following workflow needs approval before CI can run:

• periodic (gh)

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / test-models-linux-basic (mv3, xnnpack-quantization-delegation, buck2, linux.2xlarge, executorch-u... / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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

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

• pull / unittest / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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.