normalize get_lineage, get_jobs_lineage, get_downstream_lineage

[ghukill]

Lineage has evolved some, and would make sense to have methods that were more like:

• get_lineage(upstream=False, downstream=True)
  • could be drop-in replacement for get_lineage and get_downstream
  • but if upstream True, would be a "web" of connected Jobs

[ghukill]

Now that it's possible to edit input jobs via methods (https://github.com/WSULib/combine/issues/325), puts pressure to have the re-run lineage a bit smarter than id sorting.

For example, with Job 59 added after the fact as input job to Job 58, re-running 59 with downstream still has 58 re-run first (because of lower id), when in fact 59 should re-run first:

[ghukill]

Working to handle a situation like this:

Where re-run order should be: A,D,C,B,E

[ghukill]

Addressed using toposort. Handles circular dependencies -- input jobs -- for get_downstream_jobs(), but not yet for get_lineage(). Will want to include there as well.

[ghukill]

Normalized a bit. Closing here, with intent of opening more specific issues.