Cadence: Register missing portable ops (neg, exp, native_layer_norm)

[aliafzal]

Summary

• Register neg.out, exp.out, and native_layer_norm.out in the cadence backend by adding them to functions.yaml, functions_hifi.yaml, and the corresponding CMakeLists.txt files
• Remove invalid run_and_compare=False workaround from test_add_op.py
• All 357 operator tests under examples/cadence/operators/ now pass

Test plan

• Ran python -m pytest examples/cadence/operators/ -n auto — 357 passed

cc @mcremon-meta

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

⏳ 1 Pending, 2 Unrelated Failures

As of commit 984bdf3 with merge base bd99b2a ():

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

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

• pull / unittest / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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.

[meta-codesync]

@aliafzal has imported this pull request. If you are a Meta employee, you can view this in D99870895.