Wrapper deadlock detection and splits

Hello @bdepaula ,

I found an issue with infinite deadlock detection ( the normal deadlock works fine ) when the jobs wrapped have the split value set.

It is a design issue more than a bug

To know if a job could be wrapped or not in the future, AS fills a list of "next_wrappeable_jobs" and checks if the child is a direct one or not ( for vertical and 2-D wrappers, for horizontal ones is not necessary but it also does it ) to know which jobs need to be in READY status to add more jobs in the wrapper.

The problem is that the calculation only takes into account the chunks. So, for splits, this list could or could not be wrong. (For example, with the filter "previous" , this is not enough )

The idea is to change the algorithm to take into account other factors.

I think that max_jobs_to_submit, total_jobs, max_jobs, checking if other jobs can be submitted, and checking the list of active jobs could be enough to calculate the infinite deadlock without relying upon dependencies that, with the special filters, can be not so straightforward as in the past.