fix(ci): remove pytest-timeout, use per-file timeout only

fix(ci): write a new cache for test durations every time
change(ci): rip out error 4 retries because we found the real bug

tests/hermes_cli/test_cmd_update_docker.py

@@ -126,8 +126,8 @@ def test_cmd_update_on_git_install_does_not_print_docker_message(
 
     ``subprocess.run`` is mocked because the git path will otherwise shell
     out to ``git fetch upstream`` / ``git fetch origin`` — on CI runners
-    with no ``upstream`` remote configured this can hang past the 30s
-    pytest-timeout depending on git's network behaviour.  The stub
+    with no ``upstream`` remote configured this can hang past a timeout
+    depending on git's network behaviour.  The stub
     returns a successful CompletedProcess-shaped object with ``"0\\n"``
     stdout, which both keeps the flow shell-free AND parses cleanly as
     the "0 commits behind" rev-list output the check path later parses

tests/hermes_cli/test_web_server.py

@@ -4749,7 +4749,7 @@ class TestPtyWebSocket:
             while time.monotonic() < deadline:
                 # receive_bytes() blocks; once the child prints its winsize and
                 # exits, the PTY closes and further reads raise. Without this
-                # guard a missed-marker run blocks until the 30s pytest-timeout
+                # guard a missed-marker run blocks until a test timeout
                 # (flaky failure) instead of failing fast on the assert below.
                 try:
                     frame = conn.receive_bytes()