Qualcomm AI Engine Direct - Remove SKILL.md info related to AIHub and README

[winskuo-quic]

Summary

We will remove AIHUB sample code for now as it is hard to maintain since each released version has different IO's for context binary, and it is hard to create a runner for each version.
This PR removes README and SKILL.md that is related to AIHUB
We will still keep logic in backends/qualcomm for aihub in case this feature is needed again in the future.

GH stack:

• Qualcomm AI Engine Direct - Remove AIHub Example Scripts #19144
• -> Qualcomm AI Engine Direct - Remove SKILL.md info related to AIHub and README #19143

Test plan

Ensure PR does not break existing internal and external CI

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Rolling out OSDC (ARC) runners on pull & trunk workflows in PyTorch main

❌ 1 New Failure, 2 Unrelated Failures

As of commit 3af9569 with merge base bf64fa1 ():

NEW FAILURE - The following job has failed:

• Cadence Build & Test / cpu-test / test-aot / test-aot (gh)
  backends/cadence/aot/tests/test_replace_ops_passes.py::TestReplaceOpsPasses::test_replace_transposed_conv_with_linear_4

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

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

• pull / unittest / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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.

[winskuo-quic]

Hi @abhinaykukkadapu,
This PR is to remove AIHub Example Scripts as we are no longer maintaining the example scripts. The reason is that it is almost impossible to maintain and runner since the IO's for each AIHUB context binary released is not bc e.g., some has 5 IOs and next version probably has 10.

I am trying to break this PR into 2 parts using gh stack, which is what you have mentioned last time since our PR is too big sometimes. I am still try to learn how it works and will try to break it more evenly in future PRs to make it easier to review.

Currently, I am unsure how gh stack works with open-source project and would appreciate it if you can provide some guidance. I am assuming my #19144 should be on top of this PR(#19143). However, since I am merging from codelinaro, this PR(#19143) is not visible to #19144. I would like to know how Meta deals with this issue and how does gh stack merging into mainline works.
Thanks