Move optimization passes from opt_level=0 to opt_level=1 (#18206)

[mcremon-meta]

Summary:

Many passes in the cadence backend were incorrectly placed at opt_level=0
with outdated comments claiming ops like mm, repeat, scalar_tensor, full_like
were 'not supported'. These ops have portable kernel fallbacks, so
the passes are optimizations, not correctness requirements.

This diff:

1. Moves 18 passes from opt_level=0 to opt_level=1:

   • replace_ops.py: ReplaceLogicalNotBooleanWhereWithWherePass,
     ReplaceSafeSoftmaxWithSoftmax, ReplaceSqueezeAndUnsqueezeWithViewPass,
     ReplaceFunctionallyEquivalentOpTargets, ReplaceMMWithAddMMPass,
     ReplaceConvolutionOptionalArgsWithConcreteArgsPass, ReplaceRepeatWithCatPass,
     ReplaceScalarTensorWithFullPass, ReplaceFullLikeWithFullPass,
     ReplaceInfArgInFullWithValuePass, ReplaceMatmulWithTransposedMatmulPass
   • remove_ops.py: RemoveCloneOpsTransformImported, RemoveDetachCopyPass,
     RemoveZeroSizedCatArgsPass, RemoveNopExpandOpPass, RemoveToOpsPass,
     RemoveAliasCopyOpPass
   • decompose_ops.py: DecomposeAtenApproxGeluPass
   • simplify_ops.py: SimplifySliceOpPass

2. Updates docstrings to remove incorrect 'not supported' claims and
   clarify these are optimizations with portable fallbacks available.

Reviewed By: ethansfng

Differential Revision: D96766073

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ You can merge normally! (2 Unrelated Failures)

As of commit 0626c21 with merge base 569cf41 ():

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

[meta-codesync]

@mcremon-meta has exported this pull request. If you are a Meta employee, you can view the originating Diff in D96766073.

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

[digantdesai]

Any OSS visible impact from this? Stamping to unblock you.