Use wrappers from xnnpack.h for unary and binary ops (#11584)

[abhinaykukkadapu]

Summary

This PR uses xnn_define_binary and xnn_define_unary to define XNNPack ops, instead of separately calling the individual definitions.

Further changes:

1. Removes individual node definitions for unary and binary ops
2. Creates a wrapper macro to generate function defs for individual ops using xnn_define_binary and xnn_define_unary inside.

Fixes #11584

Test plan

## Build steps
cmake -DEXECUTORCH_BUILD_XNNPACK=ON ..
cmake --build cmake-out -j9

Tests ran:
./test/run_oss_cpp_tests.sh
.
.
.
100% tests passed, 0 tests failed out of 86

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ No Failures

As of commit f39f3ee with merge base 7b39a0c ():
💚 Looks good so far! There are no failures yet. 💚

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

[abhinaykukkadapu]

@pytorchbot label "release notes: none"

[abhinaykukkadapu]

lint runner failure seems unrelated. Local lint run is successful:

$ lintrunner -a
Warning: Could not find a lintrunner config at: '.lintrunner.private.toml'. Continuing without using configuration file.
  FLAKE8 success!
  CMAKE success!
  CLANGFORMAT success!
  UFMT success!
  ETCAPITAL success!
  NEWLINE success!
  NOTORCHINC success!
  NOSTDINC success!
  MYPY success!
  LICENSELINT success!
  TORCH_AO_IMPORT success!
ok No lint issues.
Successfully applied all patches.

[mcr229]

Seems like a transient issue with lint runner for now. Thanks for taking this up. In XNNCompiler we have large switch statements that look like this:

executorch/backends/xnnpack/runtime/XNNCompiler.cpp

Line 2058 in cf252a8

DefineNodeFunc getDefineNodeFunc(fb_xnnpack::XNodeUnion nodeType) {

since the define_binary/unary all look like pretty much the same implementation, would it be possible to refactor some of these _DEFINE into _DEFINE_UNARY, _DEFINE_BINARY So that we don't need custom defineSubNode, defineAddNode. I know for a couple unary configs there is some variation with alpha so there is custom logic there, but this would defintely help a lot for readability.

[abhinaykukkadapu]

@mcr229 please let me know if you suggest any more tests.