Don't assert for symbolic stride in dim_order_from_stride()

[pssrawat]

Summary:
Curently dim_order_for_stride() checks if any stride is 0, and fails if so. N7613577 shows a min repro from factorized joiner usecase with symbolic stride, where this check fails: P2015309933
This diff skips the assert for symbolic strides.

Differential Revision: D85875885

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• ROCm failures during provisioning step due to network issues

❌ 6 New Failures, 4 Unrelated Failures

As of commit 87dc06d with merge base 55452bf ():

NEW FAILURES - The following jobs have failed:

• Build Windows Wheels / pytorch/executorch / build-wheel-py3_10-cpu (gh)
• Build Windows Wheels / pytorch/executorch / upload / upload-wheel-py3_10-cpu (gh)
  Unable to download artifact(s): Artifact not found for name: pytorch_executorch__3.10_cpu_x64
• pull / android / run-emulator (gh)
  The process '/usr/bin/sh' failed with exit code 255
• pull / unittest / windows / windows-job (gh)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq
• pull / unittest-arm-backend-with-no-fvp (test_pytest_ops) / linux-job (gh)
  RuntimeError: Command docker exec -t cffa4f5ed1ef175cfb54ba1f0b3d6e96196473beff2e67d42bcf2a72308f6507 /exec failed with exit code 1
• pull / unittest-editable / windows / windows-job (gh)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq

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

• pull / test-openvino-linux / linux-job (gh) (similar failure)
  ##[error]The operation was canceled.
• pull / test-vulkan-models-linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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

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

• pull / test-binary-size-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-setup-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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

[meta-codesync]

@pssrawat has exported this pull request. If you are a Meta employee, you can view the originating Diff in D85875885.