Expose ET errors as is

[bsoyluoglu]

Summary:
This diff does two things,

1st, expose ET error as they are directly to NSErrors
2nd, deletes the unhandled exception logic as we have 0 unhandled exceptions thrown from the code so we don't need this on the bridging API.

Reviewed By: shoumikhin

Differential Revision:
D71585874

Privacy Context Container: L1322389

cc @shoumikhin @cbilgin

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 5 Pending

As of commit 448de76 with merge base 6b573af ():

NEW FAILURES - The following jobs have failed:

• Check Labels / Check labels (gh)
• Lint / lintrunner / linux-job (gh)
  >>> Lint for examples/qualcomm/utils.py:
• pull / unittest-editable / macos / macos-job (gh)
  backends/xnnpack/test/ops/test_check_quant_params.py::TestCheckQuantParams::test_inject_invalid_zp

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

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D71585874

[github-actions]

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.