Add (long) timeout for Pelita players #908
Description
(Will implement in #890 but adding here as a separate issue for transparency.)
We should set the while–recv loop in a Pelita player to exit after a timeout of maybe 60 minutes. This means that a client will wait at most 60 minutes for a new set_move request from Pelita main and exit otherwise.
This should remove any left over processes eventually that may be overlooked by our cleanup routines (doesn’t happen often but sometimes, especially during testing, some cleanup fails and then one has 20 or more Pelita clients running in the background).
This means that pausing a game in the UI for too long will basically cancel the game (resp. lead to one of the players resigning and therefore losing). (We could correct this by having the UI send a heartbeat message – and reduce the normal waiting time to something like a few minutes, but I think this should be out of the scope for now.)