[ET-VK] Add ANY_STORAGE support to expand_copy

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK] Buckify parakeet #18062
• [ET-VK][qlinear] Add bias support to q4gsw and dq8ca_q4gsw quantized linear ops #18061
• [ET-VK] Implement missing Vulkan operators for Parakeet TDT model #18059
• [ET-VK] Add ANY_STORAGE support to argmax and argmin #18058
• [ET-VK] Add ANY_STORAGE support to embedding #18057
• [ET-VK] Add ANY_STORAGE support to repeat #18056
• [ET-VK] Add ANY_STORAGE support to native_layer_norm #18055
• [ET-VK] Add ANY_STORAGE support to softmax and log_softmax #18054
• -> [ET-VK] Add ANY_STORAGE support to expand_copy #18053
• [ET-VK] Add ANY_STORAGE support to arange and full #18052
• [ET-VK] Generalize constant_pad_nd to support any storage type and packed dimension #18051
• [ET-VK] Add symint infrastructure to VulkanBackend and ComputeGraph #18050
• [ET-VK] Add Vulkan backend support for Parakeet runner and export #18049
• [ET-VK][ez] Fix IndexError in Vulkan partitioner DtypeSetList/TensorRepSetList #18048
• [ET-VK] Fix exponential blowup in tag_memory_meta_pass repset tracing #18207

Add a texture shader variant for expand_copy and a resize function for dynamic
shape support. The texture shader maps each output texel coordinate to the
corresponding input texel using modulo on the input sizes, matching the
semantics of the existing buffer shader. Use meta_ubo() instead of
buffer_meta_ubo() so the correct UBO type is selected based on storage type.
Use extract_int_or_symint_list() for target sizes to handle symbolic integers.
Register as ANY_STORAGE.

Differential Revision: D95970162

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 11 Cancelled Jobs, 1 Unrelated Failure

As of commit eda7457 with merge base 22174fa ():

NEW FAILURES - The following jobs have failed:

• Build Presets / apple (ios-simulator) / build (gh)
  The process '/opt/homebrew/bin/git' failed with exit code 1
• pull / unittest / macos / macos-job (gh)
  backends/xnnpack/test/ops/test_conv2d.py::TestConv2d::test_qs8_conv2d_bn

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• Test Metal Backend / export-model-metal-artifact (mistralai, Voxtral-Mini-3B-2507, non-quantized) / macos-job (gh)
• Test Metal Backend / export-model-metal-artifact (mistralai, Voxtral-Mini-3B-2507, quantized-int4-metal) / macos-job (gh)
• Test Metal Backend / export-model-metal-artifact (mistralai, Voxtral-Mini-4B-Realtime-2602, quantized-int4-metal) / macos-job (gh)
• Test Metal Backend / export-model-metal-artifact (nvidia, parakeet-tdt, non-quantized) / macos-job (gh)
• Test Metal Backend / export-model-metal-artifact (nvidia, parakeet-tdt, quantized-int4-metal) / macos-job (gh)
• Test Metal Backend / export-model-metal-artifact (openai, whisper-large-v3-turbo, non-quantized) / macos-job (gh)
• Test Metal Backend / export-model-metal-artifact (openai, whisper-large-v3-turbo, quantized-int4-metal) / macos-job (gh)
• Test Metal Backend / export-model-metal-artifact (openai, whisper-small, non-quantized) / macos-job (gh)
• Test Metal Backend / export-model-metal-artifact (openai, whisper-small, quantized-int4-metal) / macos-job (gh)
• Test Metal Backend / test-executorch-metal-build / macos-job (gh)
• Test Metal Backend / test-metal-backend-modules / macos-job (gh)

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / test-moshi-linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/libs/libssh/libssh-gcrypt-4_0.9.6-2ubuntu0.22.04.6_amd64.deb 404 Not Found [IP: 185.125.190.82 80]

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.