Move trunk.yml, periodic.yml and nightly.yml to linux_job_v3

[huydhn]

Fourth of six splitting up #22107. Stacked on #22247.

Also picks up the last linux_job.yml (v1) call site, in trunk's test-arm-backend-zephyr.

The two arm backend jobs that raise fs.inotify.max_user_watches now tolerate failure, since that is a node-level setting an unprivileged pod cannot change.

Authored with Claude Code.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 Pending, 1 Unrelated Failure, 6 Unclassified Failures

As of commit b8e20b1 with merge base f665a3b ():

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

• periodic / test-models-linux (buck2, mv3, portable, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (buck2, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (cmake, mv3, portable, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (cmake, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (cmake, vit, portable, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1
• periodic / test-models-linux (cmake, vit, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1

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

• pull / test-moshi-linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/libs/libssh/libssh-gcrypt-4_0.9.6-2ubuntu0.22.04.7_amd64.deb 404 Not Found [IP: 2620:2d:4000:1::103 80]

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

[huydhn]

Last commit temporarily points trunk.yml (11 refs), periodic.yml and nightly.yml at pytorch/test-infra#8683 (osdc/hf-cache-writable). Reverts to @main before landing.

Same caveats as #22247: a pull_request run already sees the label in the event payload, so this exercises the refresh path rather than the ciflow-tag resolution, and it will not seed the shared cache until meta-pytorch/pytorch-gha-infra#1463 lands.

trunk.yml is the interesting one here — it carries a ciflow/trunk tag trigger, so if a ciflow/trunk/22248 tag gets pushed, that run does exercise the tag resolution, which is the path with no coverage in test-infra.