Extend data file support for other pybindings

[lucylq]

Summary: This diff extends the support for external data_file to other executorch runtime pybindings.

Reviewed By: LeeOHzzZ

Differential Revision: D82046648

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures, 6 Cancelled Jobs

As of commit abc1c02 with merge base a1ed4ed ():

NEW FAILURES - The following jobs have failed:

• Lint / lintrunner / linux-job (gh)
  >>> Lint for extension/pybindings/test/test_pybindings.py:
• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 63cf6829bca30c75e8cb42f81add92cc8054b1f1873581dc914092654dc05a88 /exec failed with exit code 1
• pull / unittest / linux / linux-job (gh)
  backends/xnnpack/test/passes/test_channels_last_tagged_reshape.py::TestChannelsLastTaggedReshapePass::test_q_dq_nodes_around_copy_are_tagged

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

• periodic / test-models-linux (buck2, mv3, portable, linux.2xlarge, 90) / linux-job (gh)
• periodic / test-models-linux (buck2, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh)
• periodic / test-models-linux (cmake, mv3, portable, linux.2xlarge, 90) / linux-job (gh)
• periodic / test-models-linux (cmake, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh)
• periodic / test-models-linux (cmake, vit, portable, linux.2xlarge, 90) / linux-job (gh)
• periodic / test-models-linux (cmake, vit, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh)

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

[facebook-github-bot]

@lucylq has exported this pull request. If you are a Meta employee, you can view the originating diff in D82046648.

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