Consider scheduled status of a pipeline in computing trigger status

If a pipeline is in scheduled status, it means all the jobs till then succeeded and pipeline is waiting for a specified amount of time to do the remaining. As this will most probably be out of the runner time limit, the job which waits for this trigger pipeline status is going to time out. We should just consider this a successful pipeline at that point, since all the jobs prior to it succeeded.

Why: gitlab-org/distribution/gitlab-provisioner!59 (merged) made provisioner pipeline a delayed one, which causes the trigger to identify it as not successful one, and throw a failure.