Back out "[Diff Train][pytorch/executorch] Apply fixup patch to fbsource"

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK][profiling] Add additional profiling blocks #17394
• [ET-VK][qconv2d][ez] Don't use im2col path for general convs #17393
• [ET-VK] Add nchw_to_int8x4_buffer shader for prepacking int8 staging data #17392
• [ET-VK] Layout-flexible impl of quantized binary #17391
• [ET-VK][ez] Make q8ta_conv2d use 4C1W layout #17390
• [ET-VK][ez] Add AOT support for PackedInt8_4C1W dtype #17389
• [ET-VK] Migrate to use new q8ta_conv2d ops #17388
• [ET-VK][qconv] Dynamically select between im2col path and general path #17387
• [ET-VK][qconv][ez] Make q8ta_im2col shader support stride_w != 1 #17386
• -> Back out "[Diff Train][pytorch/executorch] Apply fixup patch to fbsource" #17399

Revert D92897428 which accidentally erased from recent changes to the Executorch Vulkan backend when syncing open source and fbsource.

Differential Revision: D93012332

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 Cancelled Job, 1 Pending, 1 Unrelated Failure

As of commit 60ac598 with merge base 964c565 ():

CANCELLED JOB - The following job was cancelled. Please retry:

• periodic / test-models-linux (buck2, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh)

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

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

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.