Fix issue with noop tasks that depend on other noop tasks

[dobesv]

If you had a runnable task that depended on a noop task that in turn depended on a noop task, that depended on a runnable task, the dependency between the two runnable tasks would not be preserved. The logic that prunes out noop tasks in the dependency tree did not account for multiple levels of removal.

[dobesv]

Note: there is a major performance issue in this algorithm that I have fixed in my own fork. If you're interested in this pull request I can update it with the fix. For now I'm assuming you're not going to do anything with this pull request so there's no need to fix it.

The fix:

// Update dependencies of remaining nodes
  for (const node of nodeMap.values()) {
    const newDependencies = new Set<string>();
    const processedDeps = new Set<string>();

    // Inherit the dependencies of removed nodes we depended on
    const visitDependency = (depId: string) => {
      if (processedDeps.has(depId)) {
        return;
      }
      processedDeps.add(depId);
      if (nodeMap.has(depId)) {
        // It's still a valid node, keep in dependencies list
        newDependencies.add(depId);
      } else {
        // Node was removed, propagate dependencies from the removed node
        additionalDependencies.get(depId)?.forEach(visitDependency);
      }
    };
    node.dependencies.forEach(visitDependency);
    node.dependencies = Array.from(newDependencies);
  }