Replace GTEST_SKIP() aten guards with #ifndef USE_ATEN_LIB (3/3)

[GregoryComer]

Stack from ghstack (oldest at bottom):

• -> Replace GTEST_SKIP() aten guards with #ifndef USE_ATEN_LIB (3/3) #19485
• Replace GTEST_SKIP() aten guards with #ifndef USE_ATEN_LIB (2/3) #19484
• Replace GTEST_SKIP() aten guards with #ifndef USE_ATEN_LIB (1/3) #19483

Replace runtime if (is_aten) { GTEST_SKIP() } checks with compile-time #ifndef USE_ATEN_LIB / #ifdef USE_ATEN_LIB preprocessor guards around the entire test.

Meta test infra does not handle GTEST_SKIP well, so we use preprocessor guards to exclude aten-incompatible tests at compile time instead of skipping them at runtime.

This commit covers ops n-z (ne through var). Authored with Claude.

Differential Revision: D104739568

[pytorch-bot]

🔗 Helpful Links

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

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

• Run pull jobs on OSDC in pull requests shadow mode

❌ 2 New Failures, 1 Unrelated Failure

As of commit 4590210 with merge base 23a91d5 ():

NEW FAILURES - The following jobs have failed:

• Lint / lintrunner (gh)
  >>> Lint for kernels/test/op_tril_test.cpp:
• pull / test-multimodal-linux (gemma3-4b) / linux-job (gh)
  RuntimeError: Command docker exec -t 79129fadfa227cf81309189686c35a54954e1668ed03a6f25f229fb88a80b379 /exec failed with exit code 139

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

• pull / test-qnn-testsuite-linux / test-backend-linux (qnn, models) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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.