Bound the FreeBSD package job, which has stalled five runs running

The job builds and smoke-installs inside a FreeBSD VM on a Linux runner
and normally finishes in eight to eleven minutes. Five consecutive runs
instead sat in the VM step for 70, 190, 360, 360 and 360 minutes and
ended cancelled, the last three at GitHub's default six-hour job ceiling.
The 70 and 190 minute runs are not explained by that ceiling.

The job set no timeout-minutes, so nothing of ours bounded them. Thirty
minutes leaves a slow run room to finish and turns a stall into a
half-hour failure rather than a six-hour one. This does not diagnose the
stall; it stops it costing a runner day.

The boundary is sharp and the same on both trunks: every run carrying the
native datagram API commits has stalled, and every run before them
passed. That is a correlation with a candidate mechanism and not a cause,
and it is recorded in the tracker rather than asserted here.

.github/workflows/package-freebsd.yml

@@ -58,6 +58,13 @@ jobs:
     # major (FreeBSD:15:amd64) — pkg on other majors refuses the package.
     runs-on: ubuntu-latest
     needs: determine-versioning
+    # Successful runs of this job take 8 to 11 minutes. Five consecutive runs
+    # in August 2026 instead sat in the VM step for 70, 190, 360, 360 and 360
+    # minutes and ended cancelled, the last three at GitHub's own six-hour job
+    # ceiling. Nothing here bounded them. This bound is deliberately loose
+    # enough that a slow-but-working run still passes, and tight enough that a
+    # stall fails in half an hour instead of burning a runner for six.
+    timeout-minutes: 30
 
     steps:
       - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6