consecutive_failures 0 == 1 in HealthCheck.

When defining a HealthCheck with consecutive_failures=0 one would expect Mesos to never kill the task and only notify about the failure.

What seems to happen instead is Mesos handles consecutive_failures=0 as consecutive_failures=1 and kills the task after 1 failure.

Since 0 isn't the same as 1 this seems to be a bug and results in unexpected behaviour.