Collection/Sequence use correct Status_Running

The way how Collection/Sequence is implemented is that we have it's own internal job that's run first.

The issue with is that once this job have completed collection->status() will return Status_Success even while other jobs are still running.

This is not really expected and more like leaking implementation detail.

So this MR fixes that Collection/Sequence will count as running until all jobs have finished or till first failure.

Regarding keeping status as failed even if there are still more jobs running could be debatable.

But the final end status will be failure anyway so I thought there's no harm in telling about it as soon as we know.