ci/b2c: allow defining a boot watchdog

This will be helpful for DUTs that do not boot reliably due to firmware
issue as it will allow us to specify a boot retry count that only
counts towards booting linux and not other issues found during test
execution (like hitting a GPU hang).

Signed-off-by: Martin Roukala (né Peres) <martin.roukala@mupuf.org>
Reviewed-by: Eric Engestrom <None>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32572>

.gitlab-ci/b2c/b2c.yml.jinja2.jinja2

@@ -27,6 +27,12 @@ timeouts:
     retries: 0
     # no retries possible here
 
+  watchdogs:
+    boot:
+      minutes: {{ timeout_boot_wd_minutes | default(0, true) }}
+      seconds: {{ timeout_boot_wd_seconds | default(0, true) }}
+      retries: {{ timeout_boot_wd_retries | default(0, true) }}
+
 console_patterns:
     session_end:
         regex: >-
@@ -45,6 +51,20 @@ console_patterns:
           {{ job_warn_regex }}
 {% endif %}
 
+{% if boot_wd_start_regex and boot_wd_stop_regex %}
+    watchdogs:
+        boot:
+            start:
+              regex: >-
+                {{ boot_wd_start_regex }}
+            reset:
+              regex: >-
+                {{ boot_wd_reset_regex | default(boot_wd_start_regex, true) }}
+            stop:
+              regex: >-
+                {{ boot_wd_stop_regex }}
+{% endif %}
+
 # Environment to deploy
 deployment:
   # Initial boot