Ship parent history query authority in Server 2.5.8

[rmcdaniel]

Change

Ship Workflow 2.5.2 in Server 2.5.8 to fix native HTTP queries waiting on multiple child workflows. Query replay waits for child outcomes committed to the parent history instead of advancing from terminal child rows.

Add an HTTP regression for completed, failed, cancelled and terminated children. Repeated queries preserve runtime records before and after parent resolution, restore authored result order and select the earliest recorded failure. The fixtures use explicit distinct resolution timestamps to avoid depending on execution speed.

Synchronize the existing release consumers and Helm chart 0.1.145. Only the Workflow package changes in the Composer lock.

Verification

• Unchanged locked Workflow 2.5.1 fails all four HTTP boundary cases.
• Published Server 2.5.7 reproduces premature advancement through its actual HTTP endpoint.
• Installed Workflow 2.5.2 passes the four new cases plus the existing legacy-version query case, 5 tests and 129 assertions.
• Pint and source-release consistency pass.
• Normal repository checks and published image verification follow before delivery.

Tracks durable-workflow/workflow#644. Keep that issue open until the image and affected consumers are verified. No portable SDK contract or Cloud deployment changes.

Delivery

Merged at fac053399ee5c1cdc6a150714293019e79053718 with the qualified source tree. Every normal PR/main gate passes. Server 2.5.8 is published for both architectures at sha256:54090ee28b7744361b99561290a55611d2a7e09d6ea1a8851da0f0ed6befa3b5. First-run, Compose, protocol and Helm 0.1.145 publication pass. Actual HTTP passes all four terminal-child boundaries and repeated-query immutability. All 31 published replay scenarios pass with PHP/Python/Rust workers. The isolated PHP SDK probe passes all 30 normal assertions. Delivery is complete on Workflow #644. Remote head branch and completed query-test resources are removed.