[ET-VK] Modernize permute op with safe indexing and unified dispatch

[SS-JIA]

Stack from ghstack (oldest at bottom):

• (to be filled)

Modernize the permute operator to follow current best practices, fixing an
Adreno 740 driver crash caused by dynamic UBO indexing in the texture shader.

Texture shader changes:

• Replace old indexing_utils.h with indexing.glslh
• Use TextureMetadata UBOs instead of push constant sizes
• Use texture_pos_to_tensor4d_idx_simple() and related helpers
• Replace permute_dims[out_packed_dim] with safe_idx() to avoid
  dynamic indexing of push constant with spec-const-derived index
• Use TextureElementIndex pattern for the slow path

C++ dispatch changes:

• Merge add_permute_node() and add_permute_buffer_node() into a single
  unified function using graph.meta_ubo() and conditional logic
• Remove unused channel_info computation
• Move WHCNPermuteDims struct into anonymous namespace
• Guard texture path with VK_CHECK_COND(permute_ndim <= 4)

Differential Revision: D98220451

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 9 New Failures, 2 Unrelated Failures

As of commit 672416e with merge base 8f1b5ee ():

NEW FAILURES - The following jobs have failed:

• pull / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh)
  RuntimeError: Command docker exec -t 8b866d153a8b451fa1db8a56165130ce18213c720f3cbfab104d8ee6416b8acb /exec failed with exit code 92
• pull / test-vulkan-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t a58395d2592d08fb1b24271b0de008b14fad92447188876affd3e14dd72ea6dd /exec failed with exit code 1
• pull / test-vulkan-operators-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 14f27d9a926a3a93a89ef2657d8a66524d142433ff069f02e5d1bcda5470c6a8 /exec failed with exit code 1
• pull / unittest / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 245712d93658eb7f18bb170f3067d3b15f960b4a3c31571c9d080cd15b750906 /exec failed with exit code 2
• pull / unittest-editable / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 5ade0e9b8c1dd08c207fb2f86b578c41f185b4e0e318aea04dd22bda780d8599 /exec failed with exit code 2
• Test ARM Backend / test-arm / test-backend-linux (arm_vgf_fp, models) / linux-job (gh)
  RuntimeError: Command docker exec -t 20d1bd402e166277f3ad93e7e4c748e10ff7f6a7485162e562a1ab165dfcde70 /exec failed with exit code 2
• Test ARM Backend / test-arm / test-backend-linux (arm_vgf_fp, operators) / linux-job (gh)
  RuntimeError: Command docker exec -t e78eded633d44680aa05e293d4acf5b7a07fb0d6c79ddb22066c31ee6b5eab1e /exec failed with exit code 2
• Test Vulkan Backend / test-vulkan / test-backend-linux (vulkan, models) / linux-job (gh)
  RuntimeError: Command docker exec -t 3306cc63b3bc4c46ebab657bad796c87329b52fc3d3d0aaab9d068d4e1e54c5b /exec failed with exit code 1
• Test Vulkan Backend / test-vulkan / test-backend-linux (vulkan, operators) / linux-job (gh)
  RuntimeError: Command docker exec -t 90895ecec09d55ef5cd19bdbafb36a6c6df1f3e048ec89b8d7a6c7fd391851a2 /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

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

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