[ET-VK] AOT logic for quantized conv2d

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK] Statically quantized add #14649
• -> [ET-VK] AOT logic for quantized conv2d #14648
• [ET-VK] Statically quantized convolutions #14647

Changes

As title; this diff adds the necessary export logic required to enable fusing quantized convolution patterns into the custom ops introduced in the below diff.

Differential Revision: D83437826

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures, 2 Unrelated Failures

As of commit 7bbf238 with merge base 049c9fc ():

NEW FAILURES - The following jobs have failed:

• pull / test-llama-lora-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 466e1d47cb5ce2a93b6227d306c3b818d58d1837c2d9d0c581a25f99bf118d96 /exec failed with exit code 1
• pull / test-multimodal-linux (gemma3-4b) / linux-job (gh)
  RuntimeError: Command docker exec -t 524ae23a5478ec4a9d655e9041e2825171092ce4ae9999a08c7b11620092882a /exec failed with exit code 139
• pull / unittest / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_mv3_model

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

• pull / test-binary-size-linux-gcc / linux-job (gh) (similar failure)
  ##[error]The operation was canceled.

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

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

• pull / test-setup-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

@SS-JIA has exported this pull request. If you are a Meta employee, you can view the originating diff in D83437826.

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

[facebook-github-bot]

@SS-JIA has exported this pull request. If you are a Meta employee, you can view the originating diff in D83437826.

[facebook-github-bot]

@SS-JIA has exported this pull request. If you are a Meta employee, you can view the originating diff in D83437826.