#52535: build: build siso per host so a cache miss only reruns that platform
Description of Change
Currently pipeline-segment-build-siso.yml builds all three host binaries (windows-amd64, linux-amd64, darwin-arm64) in a single matrix job, and every downstream build/publish job depends on that one job. Because GitHub Actions dependencies are job-level, a cache miss or manual re-run for a single host forced the whole siso job — and therefore every platform's builds — to re-run.
Additionally, the release jobs were running the jobs to build all three binaries, eg linux builds (or at least checks the cache for) mac: https://github.com/electron/electron/actions/runs/30454044312/job/90583265600
This PR changes pipeline-segment-build-siso.yml to include a parameter to specify which host to build for so it builds exactly one binary per invocation. Callers now instantiate one siso job per host they actually need, and each build job depends only on its own host's siso job. A cache miss or re-run for one host is now isolated to that host's builds.
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
- PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.
Release Notes
Notes: none
Backports
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron