[Windows] Reduce Windows unit test CI usage

[GregoryComer]

Trim down the Windows unit test CI. We can skip the native tests in the editable job, since they don't change at all with the python install. We can also skip the python tests in the release mode job, since it currently only builds the native tests in release mode (we always build the python extension in release mode).

[GregoryComer]

Stack from ghstack (oldest at bottom):

• -> [Windows] Reduce Windows unit test CI usage #14350
• [Windows] Reduce trunk model test count #14348

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures, 1 Unrelated Failure

As of commit 1f50fbe with merge base 108d29d ():

NEW FAILURES - The following jobs have failed:

• pull / test-static-llama-qnn-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 946608c7fb97559c6f6861708a3173d4c7c36033b088311b340c7b6bf946bf55 /exec failed with exit code 1
• pull / unittest / windows / windows-job (gh)
  Process completed with exit code 1.
• pull / unittest-editable / windows / windows-job (gh)
  Process completed with exit code 1.
• trunk / unittest-release / windows / windows-job (gh)
  Process completed with exit code 1.

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

• pull / test-llama-lora-linux / 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.