E2E Pipeline: Fix pipeline timeout

[hannojg]

We sometimes see errors in the e2e pipeline where it fails due to a 1h 30m timeout, example:

• https://github.com/Expensify/App/actions/runs/10473547848/job/29008571128

The problem is that on AWS we sometimes have to wait for 30-60 minutes, until our job is started.

We can check if the provisioning in AWS can be improved, but meanwhile we'd suggest to simply increase the timeout for the e2e job.

[hannojg]

cc @kirillzyusko

[melvin-bot]

Triggered auto assignment to @grgia, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[melvin-bot]

This issue has not been updated in over 15 days. @grgia eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[kirillzyusko]

I think that issue can be closed since the the PR was merged!