fix: track expected pipelines correctly

[cgoea]

Motivation

Fixes #57: EXPECTED_PIPELINE_TYPES treats pytorch/jax as always expected on every release, regardless of whether this release's own dispatch actually enabled them (build_pytorch/build_jax). Since #66's fix (this PR is stacked on #86 ), a platform correctly waits for every expected sibling pipeline to report before crystallizing, but a genuinely disabled pytorch/jax has no way to signal that, so it renders a wedging in_progress placeholder and holds the platform pending for the entire live window.

Technical Details

• This PR is stacked on fix: platform status stays in_progress  #86: it reuses rollup_sibling_statuses() and the per-pipeline sibling_statuses structure introduced there, so it should be merged after fix: platform status stays in_progress  #86.

Test Plan

• Added dedicated tests for the new behavior: disabled pytorch/jax renders skipped immediately and doesn't hold the platform; enabled pytorch/jax holds the platform pending past completed_at; resolves cleanly once it actually reports.
• Added tests in therock_update_status_json_test.py for the input-capture path: orchestrator-start capture, setup-run capture, missing-input default, string-bool parsing, and new-owner reset.

Test Result

442 passed

Submission Checklist

• Look over the contributing guidelines at https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.