Increase unhealthyMachineConditions timeout to 30 minutes

Address review feedback to increase timeoutSeconds from 300 (5m)
to 1800 (30m) for InfrastructureReady conditions to avoid premature
remediation during VM provisioning.

Author: rafael-azevedo

docs/book/src/tasks/automated-machine-management/healthchecking.md

@@ -62,10 +62,10 @@ spec:
       unhealthyMachineConditions:
       - type: "InfrastructureReady"
         status: Unknown
-        timeoutSeconds: 300
+        timeoutSeconds: 1800
       - type: "InfrastructureReady"
         status: "False"
-        timeoutSeconds: 300
+        timeoutSeconds: 1800
   # remediation configures if and how remediation is triggered if a Machine is unhealthy.
   remediation:
     triggerIf:

docs/book/src/tasks/experimental-features/cluster-class/write-clusterclass.md

@@ -197,10 +197,10 @@ spec:
         unhealthyMachineConditions:
         - type: "InfrastructureReady"
           status: Unknown
-          timeoutSeconds: 300
+          timeoutSeconds: 1800
         - type: "InfrastructureReady"
           status: "False"
-          timeoutSeconds: 300
+          timeoutSeconds: 1800
       remediation:
         triggerIf:
           unhealthyLessThanOrEqualTo: 33%
@@ -221,10 +221,10 @@ spec:
           unhealthyMachineConditions:
           - type: InfrastructureReady
             status: Unknown
-            timeoutSeconds: 300
+            timeoutSeconds: 1800
           - type: InfrastructureReady
             status: "False"
-            timeoutSeconds: 300
+            timeoutSeconds: 1800
         remediation:
           triggerIf:
             unhealthyInRange: "[0-2]"

docs/book/src/tasks/using-kustomize.md

@@ -99,10 +99,10 @@ spec:
   unhealthyMachineConditions:
   - type: "InfrastructureReady"
     status: Unknown
-    timeout: 300s
+    timeout: 1800s
   - type: "InfrastructureReady"
     status: "False"
-    timeout: 300s
+    timeout: 1800s
 ```
 
 You would want to ensure the `clusterName` field in the MachineHealthCheck manifest appropriately