[ET-VK] Add per-operator dtype constraints to op_registry

[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

Previously, dtype validation for Vulkan operators was scattered across
individual node-checking functions (e.g., check_to_copy_node had inline
float16/float32 checks). This made it difficult to see at a glance which
dtypes each operator supports.

This diff introduces a centralized dtype constraint system:

• utils.py: Adds dtype set constants (FP_T, INT_T, FP_INT32_T,
  FP_INT32_BOOL_T, etc.) and a DtypeSetList wrapper class with
  broadcasting semantics. The check_node_dtypes() function validates
  tensor inputs/outputs against allowed dtype sets and returns descriptive
  error messages.

• op_registry.py: Extends OpFeatures with inputs_dtypes and
  outputs_dtypes parameters. Each operator registration now explicitly
  declares its supported dtypes. Simplified node-checking functions like
  check_to_copy_node since dtype logic is now handled declaratively.

• vulkan_partitioner.py: Calls features.check_dtypes() early in
  validation, failing fast with a clear skip reason if dtypes are invalid.

This approach improves maintainability by making dtype support explicit and
centralizing the validation logic.

Authored with assistance from Claude.

Differential Revision: D92740295

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 8 New Failures, 1 Unrelated Failure

As of commit cc104d9 with merge base ba89c69 ():

NEW FAILURES - The following jobs have failed:

• pull / test-moshi-linux / linux-job (gh)
  RuntimeError: Command docker exec -t f404ca8e47a142e451d0b46b9f0b9dcf09ec15c427d93e7b545485232f414c26 /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 bec1b2edd242f2b30fe887829f37b6fc90b677cb7cab3b68fb3c7d4dd4ed9c3e /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 ac863b1ef88a6a69748d81ea0975c23bc30c9f953dda7bb5db2a981a7cce27a1 /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 70ce5cedaf4bd94bc52e6ee4264f561ce5f297f9aa57cdaebb29876f7c8ed4fd /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 4af0a1c49856057c4dc53d51ee48b565c548a07f14abe608abda6ce81bc6b4e4 /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 03e4378c7eba24fbd5a2570fe44a444b37e473d359813c9f0609db6bd846f7ee /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 0cdd90c0bfce6aef615d9732ff8dc82343a83849d9c872d0447d033431c9dc86 /exec failed with exit code 1
• Test Metal Backend / test-model-metal-e2e (openai, whisper-large-v3-turbo, non-quantized) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

BROKEN TRUNK - The following job 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-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.