fix(scenarios/major-upgrade): tolerate space after colon in gov REST status

[bdchatham]

Summary

wait-for-proposal-to-pass polls the gov v1beta1 REST endpoint and extracts the proposal status with sed:

sed -n 's/.*"status":"\([A-Z_]*\)".*/\1/p'

The API returns pretty-printed JSON with a space after the colon:

"status": "PROPOSAL_STATUS_PASSED"

The regex matched the no-space form only, so STATUS was always empty and all 300 polling attempts returned "unknown" — even though the proposal had passed on-chain.

Validated live on harbor against the running chain:

• Old regex: empty (no match)
• New regex: PROPOSAL_STATUS_PASSED ✓

One-character fix: [[:space:]]* between the colon and the opening quote.

Test plan

• Merge + ECR build → bump SCENARIO_REF + SEITASK_IMAGE on platform side
• Re-fire major-upgrade; confirm wait-for-proposal-to-pass resolves to PROPOSAL_STATUS_PASSED and the full upgrade sequence completes

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Low risk: a single regex tweak in a test workflow script to make proposal-status polling more tolerant of REST JSON formatting; no production logic changes.

Overview
Fixes the major-upgrade workflow’s wait-for-proposal-to-pass polling step to correctly parse proposal status from the gov v1beta1 REST response when the JSON contains whitespace after the colon (e.g., "status": "...").

This prevents STATUS from staying empty/unknown, allowing the workflow to reliably detect PROPOSAL_STATUS_PASSED and proceed.

^{Reviewed by Cursor Bugbot for commit dfd227e. Bugbot is set up for automated code reviews on this repo. Configure here.}