Qualcomm AI Engine Direct - fixed missing import in custom op example

[shewu-quic]

Summary:

• Resolved the visibility issue for libQnnHtp to avoid undefined symbol error with custom operator

os_linux.cc:310::ERROR:Error attempting to load dynamic library examples/qualcomm/custom_op/example_op_package_htp/ExampleOpPackage/build/x86_64-linux-clang/libQnnExampleOpPackage.so: examples/qualcomm/custom_op/example_op_package_htp/ExampleOpPackage/build/x86_64-linux-clang/libQnnExampleOpPackage.so: undefined symbol: _ZTIN4hnnx15TypicalOpIoBaseILj1ELj1EEE

• Fixed missing import in custom op example

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 4 Unrelated Failures

As of commit 5cfd120 with merge base 96aeb57 ():

NEW FAILURE - The following job has failed:

• pull / unittest / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_linear_model

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

• pull / unittest / windows / windows-job (gh) (similar failure)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 1

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

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

• Build Presets / windows (pybind) / build (gh) (trunk failure)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 1
• Build Presets / windows (windows) / build (gh) (trunk failure)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 1
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)

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.

[abhinaykukkadapu]

Please remove/ run linter. Thanks!

[shewu-quic]

Thanks!