[ET-VK][ez] Always partition batch norm as it will be fused

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK][ez][qconv] Add auto-selection to prefer im2col for q8ta_conv2d #17568
• [ET-VK][q8ta] Fix addmm arg indexing in QuantizedLinearMatch #17567
• [ET-VK][q8ta] Add q8ta_linear_gemv op for batch-1 int8 linear #17566
• [ET-VK][q8ta] Add q8ta_linear operator for int8 quantized linear #17565
• [ET-VK][export] Update tensor representation sync logic to allow for flexibility in memory layouts #17564
• [ET-VK] Support different input layouts in q8ta_binary operator #17563
• -> [ET-VK][ez] Always partition batch norm as it will be fused #17508
• [ET-VK] Add fused q8ta_relu unary operator for int8x4 tensors #17507
• [ET-VK][qconv] Add apply_relu support to q8ta conv operators #17506
• [ET-VK][qconv] Pad weight_sums buffer to multiple-of-4 alignment #17505
• [ET-VK][qconv] Fix depthwise weight_sums sum dimension #17504

The batch norm operator registration had a check_batch_norm_node guard that restricted partitioning to 4D input tensors only. Since batch norm is always fused with adjacent operations during graph compilation, this restriction is unnecessary and prevents valid models from being partitioned to the Vulkan backend. Remove the guard so batch norm is always eligible for Vulkan partitioning regardless of input dimensionality.

Differential Revision: D93511630

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 6 New Failures

As of commit 0f351d4 with merge base 7b843e4 ():

NEW FAILURES - The following jobs have failed:

• pull / test-openvino-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 35c05db06335cad0e2c95495d050102cf48216c246d43479e97a9565c8910530 /exec failed with exit code 1
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t 05cc2f4a9b5319cb632cea1cdd792296f840832aa8cc2cded0d2d63a7d6e1da7 /exec failed with exit code 1
• Test CUDA Builds / check-all-cuda-builds (gh)
  Process completed with exit code 1.
• Test CUDA Builds / export-model-cuda-artifact (nvidia, parakeet-tdt, quantized-int4-weight-only) / linux-job (gh)
  RuntimeError: Command docker exec -t d1226d37447f447dbef492dd1ca3f0dcdc6a03e099d08829528954620f114036 /exec failed with exit code 1
• Test CUDA Builds / test-executorch-cuda-build-12.8 / linux-job (gh)
  RuntimeError: Command docker exec -t f0d18d16d0fc2e3d32cba13828311122778d30c9543be9e3f9b634a5d647574d /exec failed with exit code 1
• Test Metal Backend / export-model-metal-artifact (mistralai, Voxtral-Mini-3B-2507, quantized-int4-metal) / macos-job (gh)
  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.