Let the push-to-main Test job run for 90 minutes

[MaxGhenis]

Fixes #640

Problem

Every push run on main on 16 Oct had Test jobs cancelled at exactly 60 minutes:

• the merge of Refuse disclosure codes that match nothing, and key UK regions on GSS codes #638 (run 38899177987);
• the merge of Close the receipt stack's outstanding review Lows #632 (run 38901635564);
• the merge of Qualify UK model and data candidates automatically before promotion #574 (run 38906243015).

Versioning needs Test, so it was skipped. Nothing was released: no PyPI version, and no policyengine-release dispatch to the API, sim-api, the Budget dashboard or the scorecard. Automatic UK promotion (#635) moves main and then relies on this same release path.

Successful push-run Test jobs since 14 Oct took:

Python	Minutes
3.11	33–54 (n=16)
3.12	32–56 (n=15)
3.13	36–60 (n=16)
3.14	23–42 (n=18)

#631 raised the pull-request Test job to 90 minutes on 15 Oct for the same reason. The push job was left at 60.

Change

• push.yaml Test: timeout-minutes: 60 changed to 90, with today's durations in the comment.
• changelog.d/640.fixed.md

No other job changes. A hung job still fails long before GitHub's 6-hour default.

axiom: n/a: CI configuration only.

🤖 Generated with Claude Code

[MaxGhenis]

Merged at reviewed head 3c98874 with a merge commit. Gates: gh pr checks exit 0 (13/13 pass), mergeable, no change requests. Independent review: GPT-6.1 Sol APPROVE at 3c98874 (it confirmed the cancelled jobs ran 60m17s–60m23s, with tests still passing near the cut). This PR's own Test jobs took up to 1h6m, so the 60-minute push limit would have cancelled the next release too.

🤖 Generated with Claude Code