workflows: fix linux-ci timeout for full test suite execution

The linux-ci test mode was timing out after 2 hours when executing full
fstests baselines. This mode runs make fstests-baseline which executes
the complete test suite, taking 4-8 hours depending on the profile
complexity. The xfs_reflink_4k profile, for example, typically requires
4-6 hours to complete all tests.

The workflow now uses conditional timeouts based on the test mode.
Quick validation via kdevops-ci continues using a 2-hour timeout as it
only runs a single test. Full test suite execution via linux-ci and
scheduled runs now gets 6 hours, which provides adequate time for
baseline completion with a reasonable safety margin.

GitHub Actions enforces a hard limit of 5 days (7,200 minutes) for jobs
on self-hosted runners. This limit is documented in CI-TIMEOUT-NOTES.md
along with implications for future soak duration testing support. The
pathological soak duration setting (48 hours per test across 46 tests)
would require approximately 92 days of serial execution, which exceeds
GitHub Actions limits and will require dedicated infrastructure or
parallel execution strategies.

Generated-by: Claude AI
Signed-off-by: Daniel Gomez <[email protected]>

Author: dkruces

.github/workflows/kdevops.yml

@@ -272,7 +272,13 @@ jobs:
               || 'kdevops-ci'
             }}
           tests: ${{ github.event.inputs.tests || '' }}
-        timeout-minutes: 120
+        # Timeout: linux-ci runs full test suite (6 hours), kdevops-ci runs single test (2 hours)
+        timeout-minutes: >-
+          ${{
+            (github.event_name == 'schedule' && 360)
+            || (github.event.inputs.test_mode == 'linux-ci' && 360)
+            || 120
+          }}
 
       - name: Archive results
         uses: ./.github/actions/archive