ci: extend Python test timeout to 30 minutes

[huangruiteng]

Summary

• raise the Linux pytest job timeout from 25 to 30 minutes
• retain the existing job-level fail-safe and test commands
• allow headroom for hosted-runner variance and coverage collation; PR test(authority): add the shared-goal-authority E2E stage ladder #3869 has already completed the same required job in about 16 minutes 37 seconds

Validation

• workflow YAML parse
• git diff --check
• loopx canary premerge --from-git-diff --goal-id loopx-meta: 2/2 selected checks passed, zero holds
• public/private boundary scan passed
• strict change-quality receipt: cqr_fe94dc2f56af5fd03c2b

Scope

One workflow file only. No test selection, coverage threshold, permissions, production runtime, or application behavior changes.

[huangruiteng]

No actionable findings.

Product/architecture judgment: the repository already owns the Python-suite fail-safe in one workflow-level timeout-minutes value. Raising that bounded value from 25 to 30 minutes directly addresses hosted-runner variance without changing test selection, coverage, permissions, or production behavior; a new retry or split workflow would add unnecessary ownership and scheduling complexity for this case.

Validation:

• GitHub required pytest: passed in 11m41s under the 30-minute budget
• Windows PowerShell: passed
• DCO and dependency review: passed
• workflow YAML parse and git diff --check: passed
• LoopX premerge: 2/2 selected checks passed, zero holds
• strict receipt: cqr_fe94dc2f56af5fd03c2b

Merge decision: self-merge under the owner's explicit authorization for the PR #3869 CI-timeout repair.