fix(ci): bump tests/ timeout 120s → 300s to match release workflow

The CI Go matrix step ran `go test -timeout 120s ./tests/ ./pkg/beacon/`,
which has been right at the limit for months — the tests/ integration
suite reliably takes 120-140s on the GitHub runners (heavy UDP socket
churn). After the recent additions it tipped past the ceiling and
both Go (ubuntu-latest) + Go (macos-latest) started failing with
"panic: test timed out after 2m0s".

Release workflow already uses -timeout 300s. Pre-push hook uses
-timeout 300s. Coverage step (same file) had the same 120s issue.
Aligned all three on 300s so the surfaces don't disagree.

Not a code fix — the test suite hasn't regressed, the limit was too
tight. Local runs and the release workflow have passed throughout.

Author: teovl

.github/workflows/ci.yml

@@ -36,12 +36,17 @@ jobs:
           go build ./cmd/updater
 
       - name: Test
-        run: go test -parallel 4 -count=1 -timeout 120s ./tests/ ./pkg/beacon/
+        # 300s matches the release workflow + pre-push hook. The tests/
+        # integration suite reliably takes 120-140s on these runners
+        # (lots of UDP socket churn), which was right at the prior 120s
+        # ceiling and tipped over after some recent additions. Bumped
+        # to the same budget as release.yml so the two surfaces agree.
+        run: go test -parallel 4 -count=1 -timeout 300s ./tests/ ./pkg/beacon/
 
       - name: Coverage
         if: matrix.os == 'ubuntu-latest'
         run: |
-          cd tests && go test -parallel 4 -count=1 -coverprofile=coverage.out -covermode=atomic -timeout 120s
+          cd tests && go test -parallel 4 -count=1 -coverprofile=coverage.out -covermode=atomic -timeout 300s
           go tool cover -func=coverage.out | tail -1
 
   website: