Docs: add timeoutSeconds to CPLN probes (#4053)

Add `timeoutSeconds: 5` to the Control Plane readinessProbe and
livenessProbe examples so the curl `--max-time 3` budget, not the
orchestrator's default 1s probe timeout, owns the deadline — matching
the existing /ready exec probe pattern in this doc. Without it the
orchestrator can kill curl before it finishes, flaking a healthy probe.

Regenerate llms-full.txt.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: justin808

docs/oss/building-features/node-renderer/health-checks.md

@@ -269,6 +269,7 @@ spec:
             - http://localhost:3800/health
         periodSeconds: 5
         failureThreshold: 3
+        timeoutSeconds: 5 # exceed curl --max-time 3 so the probe, not the orchestrator, owns the timeout
       livenessProbe:
         exec:
           command:
@@ -280,6 +281,7 @@ spec:
             - http://localhost:3800/health
         periodSeconds: 10
         failureThreshold: 3
+        timeoutSeconds: 5 # exceed curl --max-time 3 so the probe, not the orchestrator, owns the timeout
 ```
 
 Do **not** point a `--fail` Command probe at `/ready` unless something pre-warms the renderer, or the probe will fail

llms-full.txt

@@ -15513,6 +15513,7 @@ spec:
             - http://localhost:3800/health
         periodSeconds: 5
         failureThreshold: 3
+        timeoutSeconds: 5 # exceed curl --max-time 3 so the probe, not the orchestrator, owns the timeout
       livenessProbe:
         exec:
           command:
@@ -15524,6 +15525,7 @@ spec:
             - http://localhost:3800/health
         periodSeconds: 10
         failureThreshold: 3
+        timeoutSeconds: 5 # exceed curl --max-time 3 so the probe, not the orchestrator, owns the timeout
 ```
 
 Do **not** point a `--fail` Command probe at `/ready` unless something pre-warms the renderer, or the probe will fail