Remove type dispatch for quantized_conv1d ops

[mcremon-meta]

Summary:
Remove typed quantized_conv1d operator variants and their implementations to start fresh. This removes:

• Type dispatch logic from type_dispatch.py
• Type dispatch tests from test_type_dispatch_passes.py
• Kernel registrations from functions.yaml and functions_hifi.yaml
• Operator definitions from ops_registrations.py
• Reference implementations from ref_implementations.py
• C++ implementations from generic and HiFi operators
• Jarvis custom op definitions and argument checks

Differential Revision: D95277804

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 12 Pending, 3 Unrelated Failures

As of commit cad7421 with merge base eb77ed4 ():

NEW FAILURE - The following job has failed:

• pull / android / run-emulator (gh)
  The process '/usr/local/lib/android/sdk/platform-tools/adb' failed with exit code 224

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

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

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

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

• pull / unittest / macos / macos-job (gh) (trunk failure)
  AttributeError: '_OpNamespace' 'mkldnn' object has no attribute '_is_mkldnn_acl_supported'
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  AttributeError: '_OpNamespace' 'mkldnn' object has no attribute '_is_mkldnn_acl_supported'

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

[meta-codesync]

@mcremon-meta has exported this pull request. If you are a Meta employee, you can view the originating Diff in D95277804.

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