Add CoreML CI jobs for optimum-executorch models

[metascroy]

This PR:

• Bumps the optimum-executorch pin in our CI
• Adds a new script .ci/scripts/test_huggingface_optimum_model.py to test optimum-executorch models
• Adds a new trunk job to run CoreML models

Currently the following models are added:

• qwen3 (quantized)
• smollm (quantized)
• llama3 (quantized)
• olmo (quantized)

The following models can run for me locally with the script .ci/scripts/test_huggingface_optimum_model.py, but are not running in CI (requires investigation):

• bert (quantized)
• roberta (quantized)
• distilbert (quantized)
• vit

This CI job complements the other CI script .ci/scripts/test_model.sh that is based on the ExecuTorch examples repo.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 82 Pending, 1 Unrelated Failure

As of commit 9ec0ca7 with merge base 094b3c4 ():

NEW FAILURES - The following jobs have failed:

• Build documentation / build (buck2) / Build doc (gh)
  At least one of the pre-conditions you specified did not hold
• Lint / lintrunner / linux-job (gh)
  >>> Lint for .ci/scripts/test_huggingface_optimum_model.py:
• pull / test-moshi-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 6842549265dcfd0eebee9008f91e58caaf131db83d6eed519b2c622ce3a64bb8 /exec failed with exit code 1
• trunk / test-arm-cortex-m-size-test (bare_metal) / linux-job (gh)
  RuntimeError: Command docker exec -t 5cf230e0d62edd27af1c99403e3a3739e3476524401516c31377ada50f2739f9 /exec failed with exit code 1

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

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

• pull / test-openvino-linux / linux-job (gh) (trunk failure)
  AttributeError: '_OpNamespace' 'quantized_decomposed' object has no attribute 'convert_element_type'

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.