[ET-VK] Add supports_highdim field to OpFeatures

[SS-JIA]

Stack from ghstack (oldest at bottom):

• -> [ET-VK] Add supports_highdim field to OpFeatures #17337
• [ET-VK] Add per-operator dtype constraints to op_registry #17336
• [ET-VK] Reorganize op_registry.py by C++ implementation file #17335

Add a supports_highdim boolean field to OpFeatures in the Vulkan delegate op registry. This field indicates whether an operator implementation supports tensors with more than 4 dimensions. It defaults to False, meaning operators will reject high-dimensional tensors during partitioning unless explicitly opted in.

The partitioner now checks all input and output tensors of an op node for >4 dimensions via the new op_contains_high_dim_tensor utility, and skips nodes where the operator has not declared high-dim support.

Operators whose buffer-path shaders use BufferMetadata (which provides dynamic tensor indexing for arbitrary dimensionality) are marked with supports_highdim=True: binary ops, binary scalar (pow), reduce, argreduce, rotary embedding, permute_copy, view_copy, _to_dim_order_copy, squeeze_copy, unsqueeze_copy, gather, expand_copy, select_copy, slice_copy, and split_with_sizes_copy.

Differential Revision: D92740294

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 7 New Failures, 2 Unrelated Failures

As of commit be18a54 with merge base ba89c69 ():

NEW FAILURES - The following jobs have failed:

• pull / test-moshi-linux / linux-job (gh)
  RuntimeError: Command docker exec -t ec64f2fae1db580f423d70ad8511f37aabee6a60bc2218c2e39f64928378ea73 /exec failed with exit code 1
• Test CUDA Builds / test-model-cuda-e2e (openai, whisper-large-v3-turbo, non-quantized) / linux-job (gh)
  RuntimeError: Command docker exec -t 88fc43a809d067e719f8069d70bc777a227f4fce66c8e56561d83099328fff25 /exec failed with exit code 1
• Test CUDA Builds / test-model-cuda-e2e (openai, whisper-large-v3-turbo, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t 1b10deaf09c044d5e3757d3657dd530b56c93d92d0840174739d7e4aa8e0a935 /exec failed with exit code 1
• Test CUDA Builds / test-model-cuda-e2e (openai, whisper-large-v3-turbo, quantized-int4-weight-only) / linux-job (gh)
  RuntimeError: Command docker exec -t bb0dade335c43bdb2b850d3daddcf3aec785e82c3d27490ab4b342a81f13d9c9 /exec failed with exit code 1
• Test CUDA Builds / test-model-cuda-e2e (openai, whisper-small, non-quantized) / linux-job (gh)
  RuntimeError: Command docker exec -t ae2e5a3dc08a38a1e1a1686b0e0b796b9df475c6ceb83f4a378f1ad9b1203a1b /exec failed with exit code 1
• Test CUDA Builds / test-model-cuda-e2e (openai, whisper-small, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t 8949f167419684d45a7ab9fb6fa4b18b1e612462df909fa28fe8663e314979f4 /exec failed with exit code 1
• Test CUDA Builds / test-model-cuda-e2e (openai, whisper-small, quantized-int4-weight-only) / linux-job (gh)
  RuntimeError: Command docker exec -t ef067e7dc70fc698970c5bb18487af4dfe79318baa1828ee39f88c56a846f62c /exec failed with exit code 1

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

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

• Test Metal Backend / test-model-metal-e2e (openai, whisper-large-v3-turbo, non-quantized) / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• Test Metal Backend / test-model-metal-e2e (openai, whisper-small, non-quantized) / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

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.