Fix bug in nodestime
When `availableNodes` hits 0 in master, on the next move we hit UB in `TimeManagement::init()`. More generally, the UB can happen whenever `availableNodes < npmsec`.
That is because `limits.time[us] == 0` gets passed into `scaledTime`, which is then used in `log10` to define `logTimeInSec`, leading to `-inf` in `optConstant` and hence `+inf` in `optScale`, if `originalTimeAdjust < 0`. Casting that `+inf` double value to the integer valued `optimumTime` via `TimePoint(std::max(1.0, optScale * timeLeft))` is undefined behavior.
The patch clamps `scaledTime` from below to 1.
closes https://github.com/official-stockfish/Stockfish/pull/7129
No functional change