Initialise time budgets on every path
TimeManagement::init returned early when the side to move had no clock, before optimumTime and maximumTime were assigned. The guard still let the search read them, so a mismatched-colour clock used uninitialised values. Reproduce with:
position startpos
go depth 3 btime 1000
Add a CI test for this case and initialise the budgets to NoBound, writing NoBound on the early-return path.
closes https://github.com/official-stockfish/Stockfish/pull/7064
No functional change
Co-authored-by: ppigazzini <pasquale.pigazzini@gmail.com>