Support bert distilbert

[neuropilot-captain]

Summary

Add export scripts for supporting bert distilbert

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 2 Cancelled Jobs, 2 Unrelated Failures

As of commit 4e494d3 with merge base 4d6209b ():

NEW FAILURES - The following jobs have failed:

• Lint / lintrunner / linux-job (gh)
  >>> Lint for examples/mediatek/model_export_scripts/distilbert.py:
• pull / test-moshi-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 4f0130739e2f01bf71229fbcf0704971fd0d919cced5d53a3e8cb58bd68e63d3 /exec failed with exit code 1
• pull / unittest-editable / macos / macos-job (gh)
  exir/tests/test_quant_fusion_pass.py::TestQuantFusionPass::test_embedding_torchao
• trunk / test-models-macos-cpu (ic4, xnnpack-quantization-delegation) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 139

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• pull / test-binary-size-linux-gcc / linux-job (gh)
• pull / test-samsung-models-linux / linux-job (gh)

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

• pull / test-setup-linux-gcc / linux-job (gh) (similar failure)
  ##[error]The operation was canceled.

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

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

• pull / test-openvino-linux / linux-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.

[cccclai]

There is still lint error..