NXP Backend: Force backend (NeutronBackend) destructor call before neutronDeInit()

[robert-kalmar]

Summary

The NeutronBackend::destroy function shall be called before the Neutron driver's neutronDeInit() function to avoid double free. At this moment the ExecuTorch does not provide means to destroy the backend or the method outside of the method's desctructor.

Test plan

With upcomming eIQ Neutron SDK 3.1.2 the nxp-executor-runner crash, so existing unit tests covers this problem.

cc @JakeStevens @digantdesai @rascani

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• /easycla is not responding

✅ You can merge normally! (3 Unrelated Failures)

As of commit 09a0b86 with merge base 77df9b7 ():

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

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

• pull / test-static-llama-qnn-linux (stories_110m) / linux-job (gh) (trunk failure)
  test_llama_stories_110m
• pull / unittest / macos / macos-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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

[linux-foundation-easycla]

• ❌ - login: @robert-kalmar / name: Robert Kalmar. The commit (09a0b86) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[robert-kalmar]

Reviewers: The Github diff messy, the change is nesting the code block with the ExecuTorch program method instantiation to limit the lifetime of the method local variable.