Give the issue-2431 job's test step its own time limit

apt on the runner mirror sometimes crawls for minutes
(actions/runner-images#14823), which used up the job's 5-minute limit
before the test finished. Loosen the job limit to 15 minutes and limit
the test step, which normally takes about 80s, to 3 minutes.

.github/workflows/test.yaml

@@ -319,10 +319,9 @@ jobs:
        github.event.pull_request.head.repo.full_name != github.event.pull_request.base.repo.full_name) ||
       (github.event_name == 'workflow_dispatch' && github.event.inputs.test_linux == 'true')
     name: issue-2431 repro (Linux + ASAN)
-    # Bound the whole job in case anything in the test harness hangs
+    # Loose, because apt on the runner mirror can crawl for minutes; the test
-    # unexpectedly. With the fixture in place a normal run is well under
+    # step has its own tight limit.
-    # a minute either way (ASAN abort on broken HEAD, clean pass on fix).
+    timeout-minutes: 15
-    timeout-minutes: 5
     env:
       DNS_FIXTURE_PORT: "15353"
       DNS_FIXTURE_DELAY: "3"
@@ -370,6 +369,8 @@ jobs:
       - name: build test binary
         run: cd test && make test
       - name: run GetAddrInfoAsyncCancelTest
+        # A normal run takes about 80s.
+        timeout-minutes: 3
         run: |
           cd test
           ARCH=$(uname -m)