There was --minimum_viable_task_execution_duration command-line argument was
introduced which is 60s by default. It doesn't respect maxLaunchDelay completely,
and looks like a hack. For instance, if maxLaunchDelay is more than 60s for
some RunSpec, the corresponding rate limiting can be reset/removed, while
the deployment of RunSpec is being delayed.
In addition to that, on conditions like Running, Created, existing delays are
advanced to make sure that delays are applied to failures, and time taken by
provisioning containers doesn't get subtracted from them.
In the future we might implement removal of rate-limiting delays when
a corresponding RunSpec becomes healthy.