CI: Apply the Refactored Build Rules based on Arch Labels

[lupyuen]

Summary

This PR continues to enhance the CI Workflow, to skip the unnecessary NuttX Builds. The PR will update the CI Build Workflow build.yml, to call the Refactored Build Rules in arch.yml (which is a Reusable Workflow).

The original rules were migrated from build.yml to arch.yml:

• We target only the Simple PRs: One Arch Label + One Size Label (e.g. "Arch: risc-v, Size: XS")
• For "Arch: risc-v": Build risc-v-01, risc-v-02
• For "Arch: xtensa": Build xtensa-01, xtensa-02
• The above rules apply when the PR is Created or Modified
• When the PR is Merged: All targets shall be built

This PR applies the New and Updated Rules defined in arch.yml:

• For "Arch: arm": Build arm-01, arm-02, ...
• For "Arch: arm64": Build other
• For "Arch: simulator": Build sim-01, sim-02
• For "Arch: x86_64": Build other
• For Simple PRs (One Arch Label + One Size Label): Skip the macOS and Windows builds (macos, macos/sim-*, msys2) since these builds are costly and slow
• Except for "Arch: Simulator", which will enable the macOS Builds for sim-01 and sim-02
• If GitHub CLI Fails: Build all targets

The code is explained here: #13775

Impact

For Simple PRs: CI Builds shall be skipped for the targets that don't match the Arch Label. macOS and Windows builds shall be skipped (except for "Arch: Simulator").

For Complex PRs: No change, all targets shall be built

Testing

When we create a PR, the irrelevant builds will be totally omitted. (Merge PR will compile all targets, same for Others)

• Arm32: Create PR / Merge PR
• Arm64: Create PR / Merge PR
• RISC-V: Create PR / Merge PR
• Simulator: Create PR / Merge PR
• x86_64: Create PR / Merge PR
• Xtensa: Create PR / Merge PR
• Others: Create PR / Merge PR

Previously the irrelevant builds were skipped in seconds. Now the irrelevant builds (e.g. arm-01) are totally omitted for Simple PRs (e.g. "Arch: risc-v")

[nuttxpr]

[Experimental Bot, please feedback here]

NuttX PR Requirements Review

This PR appears to meet the NuttX requirements with a few minor points:

Summary:

• Clear explanation of the change's purpose and functionality.
• Links to the relevant issue for context.

Impact:

• Well-defined impact on CI builds, distinguishing between simple and complex PRs.
• No apparent impact on users, hardware, documentation, security, or compatibility.
  • Consider explicitly stating "NO" for these sections if there's truly no impact.

Testing:

• Provides extensive testing logs for various architectures and scenarios.
• Screenshots enhance the visualization of the changes' effects.
• Consider adding a brief summary of the test results within each section (e.g., "All tests passed as expected.").

Overall:

This PR is well-structured and informative. Addressing the minor points mentioned above will further enhance its clarity and completeness.

[xiaoxiang781216]

@lupyuen should we sync to apps repo?

[lupyuen]

@xiaoxiang781216 Yep I'll sync to nuttx-apps thanks!

[lupyuen]

@simbit18 Is it OK if I sync cibuild.sh -S to nuttx-apps, together with the rest of my changes? #13301

Linux: ...
          ./cibuild.sh -c -A -N -R -S testlist/${{matrix.boards}}.dat
msys2: ...
          ./cibuild.sh -g -i -A -C -N -R testlist/${{matrix.boards}}.dat

[simbit18]

@lupyuen yes it is ok