Raise publish build timeout to 10 minutes

The publish `build` job is capped at `timeout-minutes: 5`, but the build was
already running ~4m41s (references:all clones and generates docs for three
products, which is network-variable). The component-version refresh tasks added
in #339 make additional live GitHub API calls, pushing a representative build to
~5m06s — over the cap — so the job was cancelled at the Archive step and the
deploy was skipped, leaving master unpublished.

Raise the cap to 10 minutes to restore publishing and give headroom for the
network-variable build.

Signed-off-by: Michael Harp <mike@mikeharp.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: miharp

.github/workflows/build.yaml

@@ -57,7 +57,10 @@ jobs:
 
   build:
     runs-on: ubuntu-24.04
-    timeout-minutes: 5
+    # references:all clones and generates docs for three products and the
+    # component-version tasks make live GitHub API calls, so the build is network-
+    # variable and runs ~5 min; give headroom above the previous tight 5-min cap.
+    timeout-minutes: 10
     needs:
       - setup
     env: