Handle the "No timeout check" WARNings in the server log

[hannahbast]

By default, QLever has a very clear log, except for the many "No timeout check ..." warnings, which look more like debug messages. This is now fixed by [TODO: explain how it is fixed].

[sparql-conformance[bot]]

Conformance check passed ✅

No test result changes.

Details: https://qlever.cs.uni-freiburg.de/sparql-conformance-ui?cur=3ffb7b1d8ceb89786e40c71830791739bc59f91b&prev=5f28e832043b22102ad6e6e2a90bf93ff6846169

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.24%. Comparing base (5f28e83) to head (3ffb7b1).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #1635 +/- ## ======================================= Coverage 89.24% 89.24% ======================================= Files 374 374 Lines 35683 35683 Branches 4027 4027 ======================================= + Hits 31845 31846 +1 + Misses 2538 2537 -1 Partials 1300 1300 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud