[ET-VK] Contiguous buffer implementation for embedding

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK] Introduce specialized implementation for per-row reduction #15161
• -> [ET-VK] Contiguous buffer implementation for embedding #15160
• [ET-VK] Implementation of pow.Tensor_Scalar #15159
• [ET-VK][ez] Introduce a graph config setting to force resize functions to execute #15158
• [ET-VK] Introduce TextureMetadata struct #15157
• [ET-VK][ez] Allow bool tensors to be lowered to ET-VK and add uint8(bool) dtype variants for several compute shaders #15155
• [ET-VK][ez] Make pipeline executable properties be controlled by a different macro #15154
• [ET-VK][ez] Accept sample_kwargs as an argument in several test util functions #15153

Title says it all!

Also moved around some structs throughout the glslh files for better code organization.

Differential Revision: D84716456

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 2 Unrelated Failures

As of commit 477f2d3 with merge base 7349bb5 ():

NEW FAILURE - The following job has failed:

• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t 78252894d7e07cbb404b7f08889e5987ac8ce55c8147d19fef0e45ec67281f00 /exec failed with exit code 1

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

• pull / unittest-editable / linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

BROKEN TRUNK - The following job failed but was present on the merge base:

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

• pull / unittest / linux / linux-job (gh) (trunk failure)

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.