CI: Run CI Job other only for Simple x86 PR

[lupyuen]

Summary

Presently, Simple x86 PRs will run All CI Checks (across all Architectures), as reported here: #14885 (comment)

This PR fixes the CI Build Rules, so that Simple x86 PRs will run only One Single CI Job: other.

Impact

When we create or update a Simple x86 PR: Only CI Job other shall be executed.

No impact on other PRs.

Testing

We tested the updated Build Rules arch.yml:

• Arch x86 PR: Will build other only
  https://github.com/lupyuen5/label-nuttx/actions/runs/11963675871

• Board x86 PR: Will build other only
  https://github.com/lupyuen5/label-nuttx/actions/runs/11963676750

• Arch x86, Board x86 PR: Will build other only
  https://github.com/lupyuen5/label-nuttx/actions/runs/11963708940

Regression Test:

• Arch x86_64 PR: Will build x86_64-01 only
  https://github.com/lupyuen5/label-nuttx/actions/runs/11963695329

• Board x86_64 PR: Will build x86_64-01 only
  https://github.com/lupyuen5/label-nuttx/actions/runs/11963678242

• Arch x86_64, Board x86_64 PR: Will build x86_64-01 only
  https://github.com/lupyuen5/label-nuttx/actions/runs/11963712490

• Merge PR: Will build all targets
  https://github.com/lupyuen5/label-nuttx/actions/runs/11963606904

[nuttxpr]

[Experimental Bot, please feedback here]

Yes, this PR meets the NuttX requirements. The PR description clearly explains the problem (unnecessary CI runs for simple x86 PRs), the solution (updated CI build rules), and the impact (only the other CI job will run for simple x86 PRs, no impact on other PRs). The testing section provides ample evidence that the changes work as intended, including regression tests to ensure other architectures are not affected. The links to the test runs are particularly helpful.

While the provided information is comprehensive, consider adding these minor improvements to future PRs:

• Specific file changes: Mentioning the specific file(s) modified (e.g., arch.yml) in the Summary or Impact section would be helpful.
• "Before" and "After" logs: While links to CI runs are provided, including snippets of relevant log output directly in the "Testing logs before change" and "Testing logs after change" sections could offer a quicker understanding of the change's effect. Focus on the key differences. If the logs are very long, consider highlighting the relevant parts.
• Explicitly answer all Impact questions: While the impact is clear, explicitly answering each impact question (even with "NO") improves readability and ensures all potential impacts are considered. For example:
  • Impact on user: NO
  • Impact on build: YES (CI build rules changed for x86 PRs)
  • ...and so on for all impact questions.

These minor additions will make the PR even clearer and easier to review.