ci(lint): raise the lint job timeout from 30 to 45 minutes

The lint job's single-process cppcheck pass now takes 22-29 minutes:
the src tree grew about 60 % in files in ten days (210 files / 7.4 MB on
2026-10-04, 335 / 11.2 MB since 2026-10-12) while the cppcheck flags
stayed the same. Three runs on 2026-10-13 (38330125249, 38345850562,
38370789949) were cancelled at the 30-minute cap with cppcheck still
running and every earlier lint step clean. A cancelled lint is a hard
stop for the release graph, and the dry run's tests need lint to pass.

45 minutes puts the bound back where only a genuine hang reaches it.
Parallel cppcheck (-j) would be faster, but it changes cppcheck's
whole-program checks; it is left for its own change with a
findings-equivalence proof.

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>

.github/workflows/_lint.yml

@@ -23,8 +23,11 @@ jobs:
     runs-on: ubuntu-24.04
     # 15 min proved too tight on a slow runner day and a timed-out lint reads
     # as "cancelled", which the release graph must treat as a hard stop; keep
-    # a bound, but one only a genuine hang can hit (normal runtime ~5 min).
-    timeout-minutes: 30
+    # a bound, but one only a genuine hang can hit. 30 min stopped being that
+    # in 2026-10: single-process cppcheck over a src tree that grew ~60 % in
+    # files took the lint step from ~8 to 22-29 min, and three runs on
+    # 2026-10-13 were cancelled at 30 min with cppcheck still alive.
+    timeout-minutes: 45
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1