test: Give Apify builds more time in scheduled e2e templates test

[vdusek]

Summary

Two related scheduled e2e failures, both fixed by giving Apify builds more time to complete.

1. Stagehand rebuild: wait_for_finish=600 was silently clipped to 60s

The scheduled stagehand tests have been failing on every run since #1900 added the post-env_vars.create rebuild (example):

apify_client.errors.ApifyApiError: The build has not finished or was not successful.

ActorClientAsync.build()'s wait_for_finish parameter is clipped server-side to a max of 60s ("By default it is 0, the maximum value is 60"). A stagehand build (playwright + browser deps) does not finish in 60s, so actor.build() returned a still-PROCESSING build and actor.start(build=build_number) was rejected.

Fix: After triggering the rebuild, poll client-side via client.build(<id>).wait_for_finish(wait_secs=900) — which uses long-poll requests and actually waits up to the requested duration — then assert status == 'SUCCEEDED' before passing the build to actor.start().

2. apify push 120s timeout was too tight for heavier templates

The poetry-curl-impersonate-adaptive-parsel variant times out on every rerun (example):

subprocess.TimeoutExpired: Command '['apify', 'push']' timed out after 120 seconds

apify push waits server-side for the Docker build to finish before returning. The captured stderr shows a ~550 MB base image mid-download when the timeout fires — the CLI isn't hung, the build is just legitimately slower than 120s for heavier templates. Job total (522s ≈ 4 × 120s) confirms every rerun hits the same wall, so retries don't help.

Fix: Bump all three apify-cli subprocess.run timeouts (login, init, push) from 120s to 600s. The 1800s pytest-timeout per test still bounds a truly hung CLI; @pytest.mark.flaky(reruns=3) still covers transient network/CLI flakes.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.85%. Comparing base (41433a3) to head (2178830).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1909      +/-   ##
==========================================
- Coverage   92.89%   92.85%   -0.05%     
==========================================
  Files         167      167              
  Lines       11714    11714              
==========================================
- Hits        10882    10877       -5     
- Misses        832      837       +5     

Flag	Coverage Δ
unit	92.85% <ø> (-0.05%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.