[ET-VK][ez] Deprecate quantized_decomposed op implementations

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK] Re-implement (de)quantize_per_tensor.default #15721
• [ET-VK] Rename quantize/dequantize functions/shaders to be more generic #15720
• [ET-VK] Move operator specific quantize/dequantize ops to QuantizeDequantize.cpp #15707
• -> [ET-VK][ez] Deprecate quantized_decomposed op implementations #15706
• [ET-VK] Implementation of gather #15705
• [ET-VK][ez] Constrain out repsets individually #15704
• [ET-VK] Allow buffer input/output for quantize/dequantize for conv2d ops #15703
• [ET-VK][ez] Apply quantize op replacement to all argument nodes #15702

Title says it all! The current implementation of these ops are not being used, so remove them in order to save some binary size.

Differential Revision: D86674165

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures

As of commit d320d4e with merge base aba44fd ():

NEW FAILURES - The following jobs have failed:

• pull / unittest / linux / linux-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest / macos / macos-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest-editable / linux / linux-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest-editable / macos / macos-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe

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.