NXP backend: Enable initial unit tests workflow

[skywall]

Summary

Initial workflow definition for running unit tests for Neutron (NXP) backend.

cc @digantdesai @JakeStevens @robert-kalmar

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

As of commit 879128d with merge base 4559a61 ():

NEW FAILURE - The following job has failed:

• Build documentation / check-urls (gh)
  Process completed with exit code 1.

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

[skywall]

@pytorchbot label "module: nxp"

[skywall]

@pytorchbot label "release notes: nxp"

[digantdesai]

Do we have to use pytest? Can we start with just the unit tests?

[skywall]

We use pytest quite extensively - fixtures, mocking/spying, test parametrization, test skipping etc. Tests in Robert's PR are also based on pytest so it would require significant refactoring - https://github.com/pytorch/executorch/pull/10196/files#diff-5103e16cc6c48b276ba322c235272453e0442b6d19193200cd4a0e95706a605c . So if there's chance to stick with pytest, we would prefer it.

[digantdesai]

Curious, why do we need to enable PYBIND?

[skywall]

Sorry, this is my misunderstanding of how EXECUTORCH_BUILD_PYBIND should be used. I have considered it as a "mechanism to build backend-specific dependencies", because I needed to build portable_lib and also libquantized_ops_aot_lib. Removed.