#5040 Remove duplicate timeout setting

[ioanatflowcrypt]

This PR removed duplicate timeout setting

close #5040 // if this PR closes an issue

---

Tests (delete all except exactly one):

• Does not need tests (refactor only, docs or internal changes)

---

To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

• addresses the issue it closes (if any)
• code is readable and understandable
• is accompanied with tests, or tests are not needed
• is free of vulnerabilities
• is documented clearly and usefully, or doesn't need documentation

[ioanatflowcrypt]

Tried removing --timeout from AVA scripts to reduce duplicate timeout settings, but it's actually needed.

Without it, AVA uses a default timeout which is too short — our browser tests often wait minutes for a pool slot, so AVA thinks nothing is happening and kills the run:

✔ get.key@key-manager-autogen.flowcrypt.test (5m 4.7s)
✘ Timed out while running tests
311 tests were pending

The three timeout layers each cover different things:

• --timeout (AVA) — progress watchdog, resets after each test finishes
• TIMEOUT_EACH_RETRY / TIMEOUT_ALL_RETRIES (in-code) — per-test and per-test-with-retries limits
• execution_time_limit (Semaphore) — hard kill on the CI job

Removed TIMEOUT_OVERALL instead — it was 60min, always racing against TIMEOUT_ALL_RETRIES at 55min in the same Promise.race, so it could never win.

[sosnovsky]

looks good 👍