[Improve][CI] Sync build checks from workflow jobs

[DanielLeens]

What does this PR do?

Make the Apache-side Build check sync from the real workflow jobs when the fork-side reusable workflow run stays stuck in queued at the top level.

Why is this needed?

On August 17, 2026, Apache PR #11834 showed the required Build check as queued for a long time even though the linked fork workflow was already running jobs.

The current update_build_status.yml sync job copies the top-level response from GET /actions/runs/{run_id} directly. For the DanielLeens fork run 31993208976, GitHub still reported the workflow run status as queued, while the jobs endpoint already showed active execution:

• 62 jobs completed
• 18 jobs in_progress
• 7 jobs queued

That left the Apache-side check run 95280333095 being patched as queued -> queued instead of surfacing real progress.

This PR keeps the scope narrow:

1. use the workflow run html_url for details synchronization
2. when the top-level workflow run still reports queued, derive the check status from the real workflow jobs
3. map completed job conclusions back into the valid check-run conclusion set

Validation

• git diff --cached --check
• Local Node.js simulations for queued/in-progress/completed normalization and legal check-run conclusion mapping
• Live reproduction against DanielLeens/seatunnel workflow run 31993208976, which normalizes from upstream queued to derived in_progress
• Functional validation is left to GitHub CI for this workflow-only SeaTunnel CI fix