Add new GA models (next set)

[mergennachin]

Add next set of GA models

Summary:

On top of #12340

Add a few more tasks:

1. Image-Text Understanding (OpenCLIP)
2. Semantic Text Search (Sentence Transformers)
3. Document Q&A (DistilBERT QA)
4. Super resolution (Real-ESRGAN)
5. Audio Classification (AST)
6. Text Sentiment Analysis (RoBERTa)
7. Depth estimation (Depth Anything 2)

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 1 Cancelled Job, 7 Unrelated Failures

As of commit 0ad47d3 with merge base 7c300e7 ():

NEW FAILURE - The following job has failed:

• trunk / test-models-linux-aarch64 (depth_anything_v2, portable, linux.arm64.2xlarge) / linux-job (gh)
  RuntimeError: Command docker exec -t 74e2845828f34fabfb9b426eaef69142ca970b01bb4ad2f992a0746c10667a53 /exec failed with exit code 1

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

• trunk / test-models-linux-aarch64 (detr_resnet50, portable, linux.arm64.2xlarge) / linux-job (gh)
  ##[error]The operation was canceled.

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

• trunk / test-models-linux-aarch64 (emformer_join, portable, linux.arm64.2xlarge) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

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 / linux / linux-job (gh) (trunk failure)
  devtools/inspector/tests/inspector_utils_test.py::TestInspectorUtils::test_equip_debug_handle_to_export_program_success
• pull / unittest / macos / macos-job (gh) (trunk failure)
  devtools/inspector/tests/inspector_utils_test.py::TestInspectorUtils::test_equip_debug_handle_to_export_program_success
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)
  devtools/inspector/tests/inspector_utils_test.py::TestInspectorUtils::test_equip_debug_handle_to_export_program_success
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  devtools/inspector/tests/inspector_utils_test.py::TestInspectorUtils::test_equip_debug_handle_to_export_program_success
• trunk / unittest-release / linux / linux-job (gh) (trunk failure)
  devtools/inspector/tests/inspector_utils_test.py::TestInspectorUtils::test_equip_debug_handle_to_export_program_success
• trunk / unittest-release / macos / macos-job (gh) (trunk failure)
  devtools/inspector/tests/inspector_utils_test.py::TestInspectorUtils::test_equip_debug_handle_to_export_program_success

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.

[digantdesai]

@mergennachin - As I was going through this list, I realized most of them are from HF transformers. So,
(1) if we should continue adding more HF transformer based models on optimum-et, instead of here.
(2) As I looked on optimum-et[1], I saw many already there i.e. Albert, DistillBert, EfficientNet, Roberta, Swin. Even if we don't do (1) - we should deduplicate unless you have preference for keeping them in ET CI for some reason.

[1] https://github.com/huggingface/optimum-executorch/tree/main/tests/models

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.