Add timeout for Gloo adjustable by env vars

[HRezaei]

This PR adds more flexibility by allowing the developer to configure timeout for Gloo using a new env variable "GLOO_TIMEOUT".

The default value is 1800 seconds and thus we have to wait 30 minutes to get error if other required processes are not running. In experimental deployments we'd rather to set this to a smaller value to avoid 30 minutes waiting and see the timeout error sooner.

On the other hand, we need to set this to a larger value for debugging, otherwise the execution is halted and the timeout error occurs if the line by line debugging takes more than 30 minutes.

[ClementRomac]

Hi, thanks for your PR!
You are right, this 30 minutes timeout can be painful.
Would you mind adding the timeout variable as a parameter of lamorel's config instead of an environment variable? It would allow users to set this as any other parameters in lamorel (e.g. number of LLMs).

[HRezaei]

You're welcome!

Would you mind adding the timeout variable as a parameter of lamorel's config instead of an environment variable?

Yes, sure, is it OK to be directly under the lamorel_args? I mean something like this:

lamorel_args:
  log_level: info
  gloo_timeout: 1800
...

The other options are to nest it under either lamorel_args.accelerate_args or lamorel_args.distributed_setup_args even though I'm not sure if it fits there.