Another iteration of build and deploy of native MinGW toolchain with itself

[Blackhex]

In the secod iteration of the native toolchain build the following packages can be build with the toolchain from the previous iteration first and then replace their x64 variants for the second iteration toolchain build:

• mingw-w64-libtool
• mingw-w64-ninja
• mingw-w64-pkgconf
• mingw-w64-autotools
• mingw-w64-gperf

Also, the following utility packages that are part of MinGW codebse can be built afterwards:

• mingw-w64-libmangle-git
• mingw-w64-tools-git

Verified by https://github.com/Windows-on-ARM-Experiments/msys2-woarm64-build/actions/runs/14217604079.

[Copilot]

Pull Request Overview

This PR iterates the native MinGW toolchain build and deploy workflows by introducing new package jobs and updating the build-package workflow. The changes include adding several new jobs in the mingw-native-toolchain workflow to build additional packages, modifying job dependencies with updated "needs" values, and adding a new input to conditionally skip job steps in the build-package workflow.

Reviewed Changes

Copilot reviewed 2 out of 7 changed files in this pull request and generated no comments.

File	Description
.github/workflows/mingw-native-toolchain.yml	Added new package build jobs and updated dependency chains.
.github/workflows/build-package.yml	Introduced a new boolean input "if" to conditionally run steps and updated several step conditions accordingly.

Files not reviewed (5)

• .github/scripts/download-artifacts.sh: Language not supported
• .github/scripts/install-artifacts.sh: Language not supported
• .github/scripts/pthread-headers-hack-after.sh: Language not supported
• .github/scripts/pthread-headers-hack-before.sh: Language not supported
• build-native-with-native.sh: Language not supported

Comments suppressed due to low confidence (2)

.github/workflows/build-package.yml:6

• [nitpick] The input named 'if' is ambiguous since 'if' is a reserved keyword in workflow expressions; consider renaming it to a more descriptive term like 'should_run' to improve clarity.

if:

.github/workflows/mingw-native-toolchain.yml:130

• [nitpick] Passing 'needs' as an input to the called workflow can be confusing given the reserved use of 'needs' in GitHub workflows; consider renaming this input to something like 'dependency_jobs' for clarity.

needs: ${{ toJson(needs) }}

[Blackhex]

TODO: Share logic with build-native-with-cross.sh upon #10 (comment)