Set a global batch timeout for IGN requests Before: One map/durations call takes up to 5x8=40s, as each of the 5 sub requests take up to 8s. After: One map/durations call takes up to 8s, and each of the 5 sub requests take up to 5s.
Set a global batch timeout for IGN requests
Before:
One map/durations call takes up to 5x8=40s,
as each of the 5 sub requests take up to 8s.
After:
One map/durations call takes up to 8s,
and each of the 5 sub requests take up to 5s.

8s is less than the timeout applied at the load balancer level (10s),
thus when the IGN API lags we should no longer have HTTP 499 errors
and thus the backends should no longer get kicked out of the pool.

Fyi HTTP 499 errors mean the client (load balancer, 10 sec) closed
the connection before the server (python backend, 40 resp 8 sec) answered.

StartupsPoleEmploi/labonneboite,StartupsPoleEmploi/labonneboite,StartupsPoleEmploi/labonneboite,StartupsPoleEmploi/labonneboite